ConfigHubPub / ConfigHubPub/ConfigHubPlatform
Improve UI to prevent accidental edit from star context
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 80
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
Many devs have been bitten by the bug of editing a context of a property instead of adding a new context override for their setting.
E.G. dev wants to add a property override for (Dev,Prometheus,team_brown), but they go to (*, Prometheus, *) edit the context to (Dev,Prometheus,team_brown) and now there is no (*, Prometheus, *) context as default.
This has occurred enough times that i think the UI should instead have double validation check when the context of a property has changed. Or maybe at least when the context has a * in it.
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 or tests are identified in the issue. Start by locating the UI flow for editing a property's context and reproduce changing (*, Prometheus, *) to (Dev, Prometheus, team_brown); done means the UI warns or confirms before a context containing * is replaced, preserving the default context unless explicitly confirmed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100