Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

ipfs.dns does not have "recursive" option #1931

Closed
niinpatel opened this issue Mar 14, 2019 · 2 comments · Fixed by #1935
Closed

ipfs.dns does not have "recursive" option #1931

niinpatel opened this issue Mar 14, 2019 · 2 comments · Fixed by #1935
Labels
exp/novice Someone with a little familiarity can pick up help wanted Seeking public contribution on this issue P3 Low: Not priority right now

Comments

@niinpatel
Copy link
Contributor

Version:
js-ipfs version: 0.35.0-rc.0
Platform:
Windows 10 64-bit
Google Chrome Version 73.0.3683.75
Subsystem: ipfs.dns

Type: feature

Severity: Medium

Description:

go-ipfs implementation has --recursive option to resolve dns links.
js-ipfs throws this error: "Not enough non-option arguments: got 0, need at least 1"

Steps to reproduce the error:

go-ipfs:
ipfs dns --recursive ipfs.io
resolves to: /ipfs/QmTxvVbLQTm9qvh4wsdhehDGPy92LJSYiyAg5sh3X2ZaUE

js-ipfs:
jsipfs dns --recursive ipfs.io:
throws: "Not enough non-option arguments: got 0, need at least 1"

@alanshaw alanshaw added exp/novice Someone with a little familiarity can pick up status/ready Ready to be worked P3 Low: Not priority right now help wanted Seeking public contribution on this issue labels Mar 14, 2019
@alanshaw
Copy link
Member

Thanks for reporting @niinpatel, it would be great to get this implemented.

@niinpatel
Copy link
Contributor Author

niinpatel commented Mar 14, 2019

Yes, and once this feature is implemented, I think it'd be much easier to implement #1918. I'll take a shot at implementing this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
exp/novice Someone with a little familiarity can pick up help wanted Seeking public contribution on this issue P3 Low: Not priority right now
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants