ability to trigger loading states should be triggered on grandchildren, not just children
Open
Nobody has claimed this yet.
feature
P3
- Dominant language
- Python
- Stars
- 24.4k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 13
Description
currently with chained callbacks, loading states aren't triggered until the child is being updated. this is ok in certain scenarios, it shows exactly what is being updated, but undesirable in other scenarios.
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
Start with the issue description and inspect the callback and loading-state implementation in the Dash repository; no file, test, or entry point is named. Clarify whether loading indicators should propagate to grandchildren and define the expected behavior for chained callbacks before identifying the relevant tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100