Skip to content

Conversation

@achingbrain
Copy link
Member

@achingbrain achingbrain commented Jun 23, 2022

Not sure what the reasoning was behind this but we currently can't parse /dns/foo.com/... or /dnsaddr/foo.com/... so this PR fixes that.

Not sure why but we currently can't parse `/dns/foo.com/...` or
`/dnsaddr/foo.com/...` so this PR fixes that.
Copy link
Member

@lidel lidel left a comment

Choose a reason for hiding this comment

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

lgtm, but feels really weird we were missing them for so long 👀

Potential explanation:

  • /dns/ was not supported because go version did not – i filled multiformats/go-multiaddr-dns#47 to fix that
  • /dnsaddr missing here is strange, I remember resolving it was added around libp2p/js-libp2p#782, but perhaps it was always normalized to /ip* before creating Multiaddr instance, so we never noticed this gap?

@achingbrain achingbrain merged commit 53fb15f into master Jun 24, 2022
@achingbrain achingbrain deleted the fix/support-dns-and-dnsaddr branch June 24, 2022 13:43
github-actions bot pushed a commit that referenced this pull request Jun 24, 2022
### [10.2.1](v10.2.0...v10.2.1) (2022-06-24)

### Bug Fixes

* support dns and dnsaddr ([#253](#253)) ([53fb15f](53fb15f))
@github-actions
Copy link

🎉 This PR is included in version 10.2.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants