posit-dev / posit-dev/py-shiny
Request: a way to know which reactive caused invalidation (for debugging)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.8k
- Forks
- 135
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 21
Description
(Taken from https://github.com/rstudio/shiny/issues/1846)
I know that in python's Dash this is possible, see this page https://dash.plotly.com/determining-which-callback-input-changed
I don't know if in the python implementation shiny can theoretically do this or not. Wanted to bring it up to see if it might be posible.
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
No repository files, tests, or entry points are identified in the issue. Start by reviewing the linked Dash documentation and the referenced Shiny issue, then inspect the reactive invalidation flow to determine whether the triggering reactive can be exposed. Done means a defined debugging mechanism and an agreed implementation scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100