tigerconnect
Advanced tools
Changelog
[13.7.0] - 2021-03-18
groups.find()
: Errors like PermissionDeniedError
and NotFoundError
will now be properly thrown as different kinds of errors instead of always being NotFoundError
.Changelog
[12.10.0] - 2021-01-05
conversations.findAll()
: The conversation target and group members will no longer be downloaded for every conversation. This can greatly improve performance for users with large rosters.Changelog
[12.6.0] - 2020-11-30
client.calls
service for VoIP Calling. Demo app available here. Documentation to be added soon.conversations.fetchTimeline()
and conversations.selectConversation()
were causing the timeline of previously downloaded conversations to be cleared unnecessarily.Changelog
[11.7.0] - 2020-09-18
conversations.findAll()
when CStore is on and the user has a large roster with more than 200 items.messages.findAttachment()
: If an attachment cannot be located, return null
instead of throwing an error.Changelog
[10.8.0] - 2020-06-18
User
model now has a removedFromOrg
field, that if set to true
, indicates that the user has been removed from all organizations.displayName
of Removed User
.conversation.messages
would not be updated after a message was recalled or expired. As a sidenote: for most use-cases, we recommend using conversation.timeline
instead, since its contents will be sorted, up-to-date on recipient status flags, and will better reflect the content fetched during client.conversations.fetchTimeline()
calls.conversation.lastMessage
was sometimes not set to the most up-to-date value.client.conversations.clearMessageStatuses
, which is especially noticeable when viewing conversations for groups that have a very large number of messages.Changelog
[10.3.0] - 2020-05-13
client.messages.forward()
function has been deprecated in favor of forwardToUser()
, forwardToGroup()
, etc. and will throw an error if an attempt is made to use itclient.messages.send()
function has been deprecated in favor of sendToUser()
, sendToGroup()
, etc. and will throw an error if an attempt is made to use itconversations.fetchTimeline()
and conversations.selectConversation()
:
Changelog
[8.4.1] - 2020-01-31
contextId
and contextType
parametersconversations.fetchTimeline()
and conversations.selectConversation()
:
replayHistory = true
, reads all of the messages, leaves, and then rejoins, then only the very top (lowest sort_number
) of the conversation will be fetched.conversations.markAsRead()
:
conversations.find()
:
conversations.findAll()
messages.sendToUser()
:
conversation.lastMessage
Changelog
[8.0.2] - 2019-12-04
typingStatus.startTyping()
has changed, and it is now required to pass organizationId
as part of the 2nd options
parameter. See https://tigerconnect.github.io/js-sdk/api/typingStatus/startTyping for details.typingStatus.stopTyping()
has changed, and it is now required to pass organizationId
as part of the 2nd options
parameter. See https://tigerconnect.github.io/js-sdk/api/typingStatus/stopTyping for details.<random variable name> is not defined
error when instantiating the client.conversations.fetchTimeline()
and conversations.selectConversation()
:
replayHistory = true
, reads all of the messages, leaves, and then rejoins, then only the very top (lowest sort_number
) of the conversation will be fetched.itemsEstimate
might not be 0
, which can trigger a one-time fetch in that direction to make sure that there aren't any remaining items. This case should be relatively rare compared to past SDK releases.conversations.markAsRead()
:
Changelog
[8.0.0] - 2019-12-02
conversations.selectConversation()
:
Promise<Object>
, where Object contains these two fields:
addedMessages
: Number of items that were added to the TimelinepreviousFirstUnreadMessage
: A message model representing the firstUnreadMessage
before all messages in this conversation are marked as 'Read'.name
of "attachment"
will be provided.conversation:change
event removalclient.on('conversation:change', ...)
event has been removed.conversation.on('change', ...)
event has also been removed.client.models.Conversation.on('afterInject', (resource, conversation) => { /* code that uses
conversation */ })
conversations.fetchTimeline()
and conversations.selectConversation()
:
itemsEstimate
will already be set to 0
.conversation.timeline
.conversations.markAsRead()
:
Conversation
model:
firstUnreadMessage
will have an incorrect value in some situations.isUnread
will have an incorrect value in some situations.highestSortNumber
will have an incorrect value in some situations.unreadMessageCount
will have an incorrect value in some situations.Organization
model:
lastIncomingMessageSortNumber
had an incorrect value in some situations.events.connect()
:
message.shouldEnsureRecipientStatus
would sometimes have an incorrect value of false
after receiving an SSE event or downloading the timeline, which could cause message statuses to not be fetched when calling ensureRecipientStatus()
.conversations.fetchTimeline()
and conversations.selectConversation()
:
itemsEstimate
might not be 0
, which can trigger a one-time fetch in that direction to make sure that there aren't any remaining items. This case should be relatively rare compared to past SDK releases.conversations.markAsRead()
: