ScotGovAnalysis / ScotGovAnalysis/cssampling
Config variables into a list
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Optional idea: There are a lot of variables put into Global environment once run config.R and 00_setup.R
This is fine if just running the end to end process from the master script, but can make reviewing the process, troubleshooting more confusing.
Could these be stored in a list and say, list called config and then accessed by config$variable_name
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 reading config.R and scripts/00_setup.R to inventory the variables placed in the global environment, then trace their uses through the sampling process. Convert the configuration access to a named list and update references so the master script still runs end to end without relying on global variables.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- developer-experience
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100