Dependency manager does not respect config paths
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 209
- Forks
- 87
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 3
Description
If you try to use --config-path with flow deps add it will save the config file to a different location (flow.json) than the config file it read from.
It should safe to the same location it read from.
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 with the flow deps add command and its --config-path handling. Reproduce the issue using a config file at a non-default path, then trace where the dependency manager writes its configuration. Done means the updated config is saved to the same location that was read.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100