Ensure every presence event is published #164
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it?
Currently,
PresenceEvent
s are published only when the new presence differs from the previous one. However, even if there is no change in presence, the events should still be published to the SDK users. For example, when putting JsonTree-related information into the presence, it can be interpreted differently depending on the state of the JsonTree that the user is consuming.This PR ensures that every
PresenceEvent
is emitted to theDocument.eventstream
.Any background context you want to provide?
What are the relevant tickets?
Fixes #
Checklist