Split external IPFS node type
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.2k
- Forks
- 339
- Avg merge
- 3m
- Merged PRs (30d)
- 1
Description
I'd like to make it easier to use an external JS IPFS node. Could we split "External" node type into three:
- External (go-ipfs)
- External (js-ipfs)
- External (custom)
Selecting 1 or 2 would hide/disable "IPFS API URL" and "Custom Local Gateway" fields (and set them to the default values for the node type you've selected).
relates to https://github.com/ipfs/js-ipfs/issues/1563
Contributor guide
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 by tracing the browser extension settings UI for the existing External node type and how the IPFS API URL and Custom Local Gateway values are stored. Implement the three requested choices and verify that the go-ipfs and js-ipfs choices use their defaults while custom retains the editable fields. Done means each option displays the intended fields and values.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100