Add e2e test for setting custom registry remote file
Open
Nobody has claimed this yet.
cli
enhancement
registry
- Dominant language
- Go
- Stars
- 2.2k
- Forks
- 300
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 184
Description
Users can run thv config set-registry https://example.com/registry.json to set the registry to a remote JSON file.
We should add an e2e test for this scenario.
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 locating the existing end-to-end tests and the implementation or test entry point for thv config set-registry. Add coverage for setting https://example.com/registry.json, and confirm the command accepts the remote JSON file and uses it as the registry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, testing
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100