pusher-chatkit-server - npm Package Versions

0.12.0 - 2018-04-23

Changes

• Bump pusher-platform-node dependency to 0.13.0
• authenticate now returns an object like this:

{
    "status": 200,
    "headers": {
        "Some-Header": "some-value"
    },
    "body": {
        "access_token": "an.access.token",
        "token_type": "bearer",
        "expires_in": 86400
    }
}

where:

• status is the suggested HTTP response status code,
• headers are the suggested response headers,
• body holds the token payload.

If there's an error with the authentication process then the return value will be the same but with a different body. For example:

{
    "status": 422,
    "headers": {
        "Some-Header": "some-value"
    },
    "body": {
        "error": "token_provider/invalid_grant_type",
        "error_description": "The grant_type provided, some-invalid-grant-type, is unsupported"
    }
}

• Authentication no longer returns refresh tokens.

If your client devices are running the:

• Swift SDK - (breaking change) you must be using version >= 0.8.0 of chatkit-swift.
• Android SDK - you won't be affected regardless of which version you are running.
• JS SDK - you won't be affected regardless of which version you are running.

0.11.2 - 2018-04-17

Additions

• Added update_user function and example

0.11.1 - 2018-04-10

Fixes

• Fix createUser to work with avatarURL and customData

0.11.0 - 2018-04-09

Changes

• All functions now take a single object as their only argument. Check the documentation for specifics on how to make calls using the new format.

Some examples:

authenticate used to be called like this:

chatkit.authenticate("my-user-id", { grant_type: "client_credentials" })

and the new version is called like this:

chatkit.authenticate({
  userId: "my-user-id",
  authPayload: { grant_type: "client_credentials" },
})

createUser used to be called like this:

chatkit.createRoom("ham", "New room")

and the new version is called like this:

chatkit.createRoom({
  creatorId: "ham",
  name: "New room",
})

• authenticate no longer requires the grant_type to be specified. If no value for it is provided then it will take a default value of client_credentials (which was already the implicit default provided by clients)

0.10.0 - 2018-03-12

Changes

• Update jsonwebtoken dependency

Additions

• Added support for getUserRooms
• Added support for getUserJoinableRooms
• Added support for createUsers

0.9.2 - 2018-02-08

Changes

• getRoomMessages now has a signature of getRoomMessages(userId: string, roomId: number, options: GetRoomMessagesOptions = {})

Fixes

• getRoomMessages now generates a valid token when provided with an appropriate userId as the first parameter

0.9.1 - 2018-01-26

Additions

• Added getRoomMessages example

Changes

• getRooms now requires a userId parameter, which is used to generate the token that the request is made with
• Updated getRooms example
• Bumped pusher-platform-node dependency to 0.11.1

0.9.0 - 2018-01-16

Additions

• Added updateGlobalRoomPermissions example

Changes

• When using createUser the promise that is returned now resolves with the JSON response from the API (which contains the user information), if the request succeeds

Removals

• Removed permissions constants and permissions checking from the SDK. The API will return a sensible error if you provide an invalid permission name

0.8.3 - 2018-01-04

Additions

• Support cursors permissions "cursors:read:get" and "cursors:read:set"

0.8.3 - 2018-01-04

Additions

• Support cursors permissions "cursors:read:get" and "cursors:read:set"