We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
https://github.com/automerge/automerge-repo/blob/main/packages/automerge-repo-network-broadcastchannel/src/index.ts#L60
The 'peer-candidate' event is emitted with the peerMetadata of the local Peer, NOT the metadata of the peer we received the message from.
This doesn't make sense and is different from the 'MessageChannel' implementation for example.
The text was updated successfully, but these errors were encountered:
Is the senderId in this context not the one received in the message? If so, it is indeed from the new peer.
senderId
Sorry, something went wrong.
senderId is unpacked from the received message in the message handler here: const { senderId, type } = message
const { senderId, type } = message
The peerMetadata value is closed over from the call to 'connect' which receives the local peerMetadata from the NetworkSubsystem.
My apologies, I didn’t read your issue correctly at all. You are indeed correct.
Are you in a position to put in a PR?
Fixed by #287
No branches or pull requests
https://github.com/automerge/automerge-repo/blob/main/packages/automerge-repo-network-broadcastchannel/src/index.ts#L60
The 'peer-candidate' event is emitted with the peerMetadata of the local Peer, NOT the metadata of the peer we received the message from.
This doesn't make sense and is different from the 'MessageChannel' implementation for example.
The text was updated successfully, but these errors were encountered: