Changelog History
Page 1
-
v50200.11.0 Changes
API changes: (Thanks Ajay Eeralla)
- Added a new constructor
PreferenceCategoryFavoriteChannel
to thePreferenceCategory
type and updated its JSON parser to recognize this category. - Added a
FavoriteChannelPreference
type andpreferenceToFavoriteChannelPreference
smart constructor.
Other changes:
- Logging now uses
show
, nottoJSON
, for values to be logged. This changes the logging functionality to use simple Show instances instead of first converting internal data types back to AESON structures. That wasn't really providing any additional value, and the extra conversion was producing at least one inconsistency due to an unfinished ToJSON implementation. (Thanks to Karl Smeltzer (@karljs))
- Added a new constructor
-
v50200.10.0 Changes
API changes:
Types
got constructors forPreference
valuesTypes
got a newPreferenceCategoryTeamsOrder
constructor forPreferenceCategory
-
v50200.9.0 Changes
API changes:
- Added
Network.Mattermost.Types.Internal.connectionDataURL
and its return type,ServerBaseURL
, to obtain base URLs corresponding to a connection handle.
- Added
-
v50200.8.0 Changes
API changes:
- Added a
WMUnknownEvent
constructor to theWebsocketEventType
data type to hold unknown event types to avoid parse failures for new event types. - Added
mmListCommandsForTeam
to get commands for a team and implemented a JSON parser for theCommand
type.
📦 Package changes:
- Upgraded to HTTP 4000.3.15 to get an
Eq
instance fix for HTTP header name comparisons.
- Added a
-
v50200.7.0 Changes
API changes:
- Added a
WMUnknownEvent
constructor to theWebsocketEventType
data type to hold unknown event types to avoid parse failures for new event types. - Added
mmListCommandsForTeam
to get commands for a team and implemented a JSON parser for theCommand
type.
📦 Package changes:
- Upgraded to HTTP 4000.3.15 to get an
Eq
instance fix for HTTP header name comparisons.
- Added a
-
v50200.6.0 Changes
API changes:
- Version 4 API functions now all have the potential to raise a new
exception type,
RateLimitExceptions
, when HTTP 429 (rate limiting) responses are received. The new exception type provides rate limit metadata received from the server so the caller can determine whether to attempt a request again, and how long to wait before attempting it. - The
ChannelNotifyProps
type got a newchannelNotifyPropsIgnoreChannelMentions
field. - The
WEData
type got awepChannelMember
field.
Other changes:
channel_member_updated
websocket events are now parsed.- Some haddock syntax errors were fixed (thanks Eric Mertens)
- Version 4 API functions now all have the potential to raise a new
exception type,
-
v50200.5.0 Changes
API changes:
- Added support for making connections to Mattermost servers that use
non-root URL paths for their API endpoints. This change adds a new
field,
cdUrlPath
, to theConnectionData
type. It also added a URL path argument of typeText
tomkConnectionData
. (Thanks Isaiah Mindich) - Added
Network.Mattermost.Endpoints.mmGetLimitedClientConfiguration
(thanks Eric Mertens)
- Added support for making connections to Mattermost servers that use
non-root URL paths for their API endpoints. This change adds a new
field,
-
v50200.4.0 Changes
The post pinning API is now supported.
- Adds a new postPinned field to the Post type to allow parsing "is_pinned" values in post editing websocket events. Typically "is_pinned" is not present in post structures, in which case this will take the value Nothing.
- Exposes the new StatusOK type that is returned by new API functions.
- Adds new API functions:
- mmPinPostToChannel
- mmUnpinPostToChannel
- mmGetChannelPinnedPosts
The library now supports connecting to HTTPS endpoints without valid certificates.
This change gets rid of the initConnectionDataInsecure function and instead makes initConnectionData take a new argument of type 'ConnectionType' that describes how the connection should be made.
The ConnectionType type indicates that a connection should be HTTP, HTTPS with cert validation, or HTTPS without cert validation.
This change also modified ConnectionData to carry the connecion type rather than just a Bool indicating HTTP/HTTPS.
- Websocket action responses are now parsed properly.
Websocket actions, such as "user typing" notifications, generate server responses that we previously could not parse. We weren't parsing them because the parser for websocket events wasn't aware of an alternative response message structure. This patch adds a new type for action responses. It adds a new type rather than adding a new constructor to the event type because I think that's a less ugly API (the API in this patch is not ideal). This patch also adds logic to the websocket response parser to first attempt to parse incoming messages as websocket events (the most common case) and then fall back to attempting a parse as a websocket action response. If both fail, the message and the parse exceptions are all logged.
-
v50200.3.0 Changes
🐛 Bug fixes:
- Fixed a bug in the Team JSON decoder where the
invite_id
field was required despite it truly being optional (see also https://github.com/matterhorn-chat/matterhorn/issues/550)
- Fixed a bug in the Team JSON decoder where the
-
v50200.2.0 Changes
API changes:
- Added
Network.Mattermost.Endpoints.mmDeleteReaction
to delete reactions. - Added
Network.Mattermost.Endpoints.mmPostReaction
to add reactions. - Added an
Emoji
data type and functions for custom emoji search and listing:Network.Mattermost.Endpoints.mmSearchCustomEmoji
Network.Mattermost.Endpoints.mmGetListOfCustomEmoji
🆕 New features:
- Add support for SOCKS proxies via standard environment variables
HTTPS_PROXY
andALL_PROXY
. - Support
NO_PROXY
to blacklist proxied hosts.
- Added