feat: Shiny anti-pattern
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 517
- Forks
- 53
- Avg merge
- 17m
- Merged PRs (30d)
- 4
Description
Ex:
- Do not define reactive() within other reactive() or observe() calls
- Prefer reactive() calculations over reactiveValues()+observe()
- Do not use global variable state within reactive expressions
Related:
Contributor guide
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
Read the linked Reactivity/slides.Rmd sections at lines 303-314 and 440-488 to understand the Shiny anti-pattern guidance. Then locate how this repository defines skills and determine how the listed examples should be represented; done means the skill clearly covers the three stated anti-patterns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100