The-Strategy-Unit / The-Strategy-Unit/nhp_inputs

Consider a 'confirmation gate' to ensure user understanding

Open
#660 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

could inputs_selection_app
Dominant language
R
Stars
2
Forks
1
Avg merge
15h 39m
Merged PRs (30d)
6

Description

Mentioned by @Lextuga007, thank you.

Maybe we can have a confirmation pop-up/checkbox for the user to confirm what they've selected (start year, end year, scenario name, etc). And possibly that they understand what they're undertaking, that they've done training, reviewed their detailed baseline, etc.

Sure, people might just click through, but it may make some people stop and think for a second. This is useful for release in e.g. v5.0 becuase we've changed the default start year to 2024/25 and we want to make sure people have looked through their 2024/25 detailed results files.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named in the issue. Start by locating the Shiny UI flow for selecting the start year, end year, and scenario name, then review how users access detailed baseline results. Done should include an agreed confirmation gate covering the requested selections and understanding checks, with the 2024/25 workflow clearly addressed.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.