[SDK-3910] Fix RealtimePresence#leave
handling of PresenceMessage
argument
#1466
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.
RealtimePresence
’senter*
,update*
andleave*
methods all advertise themselves as accepting aPresenceMessage
instance instead of just a data object. This is the only way that ably-js supports passing message extras to these methods.However,
leave
does not handle aPresenceMessage
argument properly; it ends up nesting thePresenceMessage
’s top-level fields inside the payload’sdata
property.To fix this, we change the argument handling to match that used by
enter
.Resolves #1465.