-
Notifications
You must be signed in to change notification settings - Fork 18
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
Do not throw? #25
Labels
exp/novice
Someone with a little familiarity can pick up
help wanted
Seeking public contribution on this issue
P2
Medium: Good to have, but can wait until someone steps up
Comments
👍 |
As mentioned in multiformats/js-multiaddr#53 I think it should return true. |
That specific example aside, what I'm asking is: should any bad multiaddr that causes a throw should be caught and return e.g. |
daviddias
added
status/ready
Ready to be worked
help wanted
Seeking public contribution on this issue
exp/novice
Someone with a little familiarity can pick up
P2
Medium: Good to have, but can wait until someone steps up
labels
May 30, 2018
mkg20001
added a commit
to mkg20001/js-mafmt
that referenced
this issue
Jan 11, 2019
🎉 PR #36 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
exp/novice
Someone with a little familiarity can pick up
help wanted
Seeking public contribution on this issue
P2
Medium: Good to have, but can wait until someone steps up
mafmt.HTTP.matches('/ip4/127.0.0.1/tcp/90/http/baz.jpg')
currently throws. Would it be better for consumers of this library if it just returned false?The text was updated successfully, but these errors were encountered: