Supported topic on send-receive publish data, fix parameter mapping for DataReceived event. #74
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.
LocalParticipant.PublishData()to sendPublishDataOptionsas a structured JSON, including topic, destinationIdentities, and reliable flags.RoomEvent.DataReceivedto correctly extract and forward the topic and DataPacketKind parameters from the JS stack.Previously, the WebGL build was unable to send or receive the topic associated with a data packet, as the bridge did not forward it and read it properly. This caused topic-based message handling to fail silently in WebGL builds.
Manual testing has been performed: