fix(fluid-static):Added userData in member connection details #24485
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.
Description
We discovered a minor bug that in the Audience service
getMembers
, user data withinconnections
associated with sameuserID
was being lost when a user with the sameuserId
joined the session multiple times i.e. having multiple connections with differentclientId
.This was because only
clientId
andmode
were being stored in each connection.This PR addresses the issue by adding a
userData
field alongsideclientId
andmode
in each connection entry, ensuring that user-specific data is accurately preserved for every individual connection.