space: Ensure lock state is maintained in presence data #118
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Prior to this change, updating profile data or setting location would remove all lock state from presence since `extras` would be set to `null`, which would wrongly release all locks held my the current member. Signed-off-by: Lewis Marshall <lewis.marshall@ably.com>
lmars
force-pushed
the
fix-presence-updates
branch
from
6109c79
to
f879c06
Compare
surminus
approved these changes
Aug 22, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Prior to this change, updating profile data or setting location would remove all lock state from presence since
extraswould be set tonull, which would wrongly release all locks held my the current member.