The-Strategy-Unit / The-Strategy-Unit/data_science
Shiny development
Open
Nobody has claimed this yet.
session: C&C ☕
- Dominant language
- Jupyter Notebook
- Stars
- 11
- Forks
- 5
- Avg merge
- 5h 34m
- Merged PRs (30d)
- 1
Description
- Debugging
- {shinytest2}
- Style frameworks {bslib} ?
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 clarifying the intended scope of “Shiny development,” including debugging, shinytest2, and the possible use of bslib. Before implementation, define which development outcome is required and how completion will be verified; the issue names no files, entry points, or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- design, testing-qa, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100