All Versions
38
Latest Version
Avg Release Cycle
-
Latest Release
-

Changelog History
Page 2

  • v50200.1.4 Changes

    🐛 Bug fixes:

    • Content-type headers in server API responses are now parsed correctly in the presence of media type parameters as per RFC 2616.

  • v50200.1.3 Changes

    API changes:

    • The PostProps type got support for the from_webhook prop

  • v50200.1.2 Changes

    🐛 Bug fixes:

    • The server response to an uploaded file may report "null" for client_ids. This previously failed the parse attempt to create a Seq ClientId; this fix updates to conver null to an empty Seq. This typically manifested in attempting to attach a file in a common channel.

    Compatibility:

    • Updated supported/tested GHC versions: 8.2.2, 8.4.4, and 8.6.3.

  • v50200.1.1 Changes

    🐛 Bug fixes:

    • The userCreateAt, userUpdateAt, and userAuthData fields of User are now permitted to be optional in the user JSON encoding to be consistent with the server.

  • v50200.1.0 Changes

    • Added mmUploadFile and exposed its UploadResponse result type.
    • Fixed the FileInfo JSON decoder to permit post_id to be omitted.
    • Added RestrictDirectMessageSetting data type for clientConfigRestrictDirectMessage field of ClientConfig.
    • Added mmAutocompleteUsers.
    • Added mmAutocompleteChannels.
    • Added DirectChannelShowStatus preference type and constructor.

    🐛 Bug fixes:

    • mkQueryString now properly URI-encodes keys and values.

  • v50200.0.1 Changes

    🐛 Bug fixes:

    • Fix the specification of the QuerySince time for fetching channel posts. The previous version generated a user-displayable date-time which contained spaces and created a malformed URL as well as not being in the proper format for the server.

  • v50200.0.0 Changes

    API changes:

    • Expose new type, TeammateNameDisplayMode, as the type of the clientConfigTeammateNameDisplay field
    • Removed various fields from TeamSettings and ClientConfig that seem to have been removed in 4.9
    • Remove parent_id fields from Post and PendingPost since they are unused and thus confusing
    • Added basic parsing support for websocket events new in 5.2 (fixes #408)
    • ClientConfig: removed EnableUserCreation field that is removed in 5.0
    • Removed extra_update_at channel data field

    🐛 Bug fixes:

    • Fixed examples and tests to use the UserText type instead of Data.Text (thanks Carlos D [email protected])

  • v40900.1.0 Changes

    API changes:

    • Added a newtype, UserText, to wrap many API response fields to indicate that they may contain unsafe or unsanitized user input. Also added unsafeUserText to unwrap such values when the caller knows that using the unsafe value is appropriate.

  • v40900.0.0 Changes

    • Endpoints: enabled mmPatchPost and removed duplicate argument type for PostUpdate.
    • Ensure that file fetching uses the V4 API endpoint.

  • v40800.0.2 Changes

    • The websocket connection now uses the V4 API endpoint.
    • submitRequest now also retries on "resource vanished" exceptions.