The-Strategy-Unit / The-Strategy-Unit/nhp_inputs
Reconsider approach to upgrading params
Open
Nobody has claimed this yet.
enhancement
question
techdebt
- Dominant language
- R
- Stars
- 2
- Forks
- 1
- Avg merge
- 15h 39m
- Merged PRs (30d)
- 6
Description
We currently force upgrades to happen in the inputs selection app. Should we do it or should users get the choice? Where should we do it? Also how should we communicate this to users?
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 reviewing the current parameter-upgrade flow in the inputs selection Shiny app. Determine where upgrades are forced and how users currently encounter them, then clarify whether users should choose and what communication is required. Done means the upgrade behavior and user-facing explanation have an agreed design.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100