Aggregate data regarding the configuration structure
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.5k
- Forks
- 228
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 48
Description
Is your feature request related to a problem? Please describe.
We would like to further improve our CLI toolkit. In order to prioritise better, we have to know how popular different configuration options are among our users.
Describe the solution you'd like
In order to answer the question above, we have to aggregate the config data.
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
No files, tests, entry points, configuration options, or aggregation mechanism are named. Start by mapping how the CLI configuration is defined and loaded, then clarify which data may be collected, how it is aggregated, and the privacy requirements with maintainers. Done should include an agreed scope and measurable way to report configuration-option popularity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- analytics, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100