Skip to content
New issue

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

docs: use tag for webrtc-star discovery config #713

Merged
merged 1 commit into from
Jul 20, 2020

Conversation

vasco-santos
Copy link
Member

To avoid confusions like we previously had. This was not fixed at the time

@@ -304,7 +304,7 @@ const node = await Libp2p.create({
},
config: {
peerDiscovery: {
webRTCStar: {
[WebRTCStar.tag]: {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is referenced in the same file further down as WebRTCStar.prototype[Symbol.toStringTag], we should probably keep that consistent.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is a good point! We are using the tag's for discovery configurations everywhere. I also saw the WebRTCStar.prototype[Symbol.toStringTag] and it is being used for the configuration of a transport.
I think we should clean this up in #576 , but now I think we should guarantee consistency between all the discovery services. For transport configuration, we should use the symbol property. While for webrtct, it will be the same, for other transport/discovery it will not be.

@jacobheun jacobheun merged commit 3896941 into master Jul 20, 2020
@jacobheun jacobheun deleted the docs/use-tag-for-webrtct-star-discovery-config branch July 20, 2020 12:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants