|String||ID of the context. Will change with each update.|
|String||Type of the context.|
|Teammate||The teammate using the plugin.|
There are different context types returned when the user has a popover window open versus when there is no popover window open. Popover windows are features that developers can add to plugins that allow users to pop open a window overlay in Front while users interact with the plugin.
In most cases, a user will not have a popover window open. In this scenario, the context returns information about the conversations the user is interacting with from the normal Front workspace view.
noConversationwhen no conversation is selected by the user.
singleConversationwhen a single conversation is selected the user.
multiConversationswhen multiple conversations are selected by the user.
When a user has a popover window open, the context returns information about the conversation the user was interacting with when opening the popover window.
noConversationPopoverwhen the user is composing a brand new message in a popped out composer. Because the conversation is new, there is no conversation context, but there will be information about the draft.
singleConversationPopoverwhen the user is interacting with a single conversation and chooses to open a popover window from the composer or other UI option where popovers can be opened.
Depending on the type of context, developers have access to useful properties as described in the following table.
|Property||Type||Description||Availabe on Context types of:|
|Array of Conversation||List of the selected conversations.|
|Conversation||The conversation selected.|
|string||The current draft id the composer is composing.|