-
Notifications
You must be signed in to change notification settings - Fork 27
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: clarify use of provider hints #72
Conversation
- makes it explicit that connection dials to origins and delegates are best-effort, and should not fail the pinning - swaps examples to use fully resolved multiaddrs, that can immediatelly be acted upon (IP ranges from test ranges (https://tools.ietf.org/html/rfc5737)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some little style/grammar nits. Thanks!
Co-authored-by: Jessica Schilling <[email protected]>
Co-authored-by: Jessica Schilling <[email protected]>
Co-authored-by: Jessica Schilling <[email protected]>
Co-authored-by: Jessica Schilling <[email protected]>
Co-authored-by: Jessica Schilling <[email protected]>
Co-authored-by: Jessica Schilling <[email protected]>
Co-authored-by: Jessica Schilling <[email protected]>
Co-authored-by: Jessica Schilling <[email protected]>
Co-authored-by: Jessica Schilling <[email protected]>
Co-authored-by: Jessica Schilling <[email protected]>
@jessicaschilling thank you, applied suggestions + made a small clarification in 84cec73 – mind taking a second look? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you!
Merging as I got 👍 from @aschmahmann and @obo20 via a telepathic medium of a great accuracy. |
This PR updates docs and examples related to
origins
anddelegates
multiaddr arrays:Thanks to @obo20 for raising the ambiguity here – lmk if this clears things out.