-
Notifications
You must be signed in to change notification settings - Fork 441
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
Configure Protocol Muxing sequence #201
Labels
exp/wizard
Extensive knowledge (implications, ramifications) required
P1
High: Likely tackled by core team if no one steps up
status/ready
Ready to be worked
Comments
Merged
This was referenced Jun 28, 2018
Closed
daviddias
added
exp/wizard
Extensive knowledge (implications, ramifications) required
P1
High: Likely tackled by core team if no one steps up
labels
Jul 2, 2018
This is now an array in the config and it will prioritize based on the order, although we currently only support mplex. |
maschad
pushed a commit
to maschad/js-libp2p
that referenced
this issue
Jun 21, 2023
Updates project config to publish api docs
maschad
pushed a commit
to maschad/js-libp2p
that referenced
this issue
Jun 21, 2023
## [5.0.2](libp2p/js-libp2p-websockets@v5.0.1...v5.0.2) (2022-12-16) ### Documentation * publish api docs ([libp2p#201](libp2p/js-libp2p-websockets#201)) ([722b03a](libp2p/js-libp2p-websockets@722b03a))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
exp/wizard
Extensive knowledge (implications, ramifications) required
P1
High: Likely tackled by core team if no one steps up
status/ready
Ready to be worked
With https:/libp2p/js-libp2p/pull/166/files, the libp2p constructor will be fully refactored and with it comes the option to pass a Protocol Muxing sequence.
My proposal is on communicate this is on https:/libp2p/js-libp2p/pull/166/files#r193032278, however, I'm not married to that solution just yet. Example below:
The text was updated successfully, but these errors were encountered: