multiformats / multiformats/go-multiaddr-dns
Filtering by protocol stack
Open
Nobody has claimed this yet.
kind/enhancement
- Dominant language
- Go
- Stars
- 32
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
The -p on the CLI filters results by protocol stack. Not sure yet what the interface around Resolve() should be.
> madns -p /ip6/tcp/wss /dnsaddr/example.net
/ip6/2001:db8::a3/tcp/443/wss/ipfs/Qmfoo
/ip6/2001:db8::a4/tcp/443/wss/ipfs/Qmbar
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the CLI handling for -p and the Resolve() interface; the issue does not name files or tests. Use the /ip6/tcp/wss example to clarify the intended filtering behavior, and consider the work done when protocol-stack filtering has a defined interface and produces the shown result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100