The-Strategy-Unit / The-Strategy-Unit/tpma-explorer
Standardise back-end variables and naming
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 0
- Forks
- 2
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 1
Description
This app borrowed some code from nhp_inputs originally, so there are references to 'strategies' and 'mitigators', for example. Replace with references to 'tpma' instead. Better for consistency and understanding.
There may be other terms to change as well.
Nothing is broken, but it could be confusing for new developers.
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
Search the repository for references to “strategies” and “mitigators”, then review nearby back-end variables for related naming inconsistencies. Confirm that the terminology consistently uses “tpma” and that the Shiny app still runs without changing its behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100