Make system-level configuration optional
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 29
- Forks
- 12
- Avg merge
- 19h 37m
- Merged PRs (30d)
- 2
Description
Currently, if the system-level configuration file is not found, the initConfiguration() func will fail. This is OK in the case where the binary is installed in a system-wise fashion (e.g. through a package manager), but not in cases where it is installed locally (e.g. through go install ... or directly from a binary).
We need to make the system-level configuration file optional like all the other layers to facilitate usage with all standard ways.
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 by locating the initConfiguration() function and trace how it handles the system-level configuration file compared with the other configuration layers. Done means the system-level file may be absent without initialization failing, while existing configuration layers continue to work; run the project’s available tests or local CLI initialization checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100