Implement feature flag mechanism
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 16
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 1
Description
This will, at the moment, mostly help with removing the broken "usage" stuff on the dashboard. Going forward it will be a good way to have multiple different people do pilots with the frontend without stepping on each others toes.
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
No files, tests, or entry points are named. Start by locating the dashboard's broken "usage" functionality and the existing frontend configuration or pilot workflow, then determine the scope of a feature-flag mechanism that supports multiple pilots without conflicts. Done should include an agreed design and a working way to enable or remove the relevant dashboard behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100