Namespacing component ID support for large or multi-page apps
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 24.4k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 13
Description
I wanted to use a code example - loaded with tools.load_example- more than once and found I couldn't because of errors regarding the outputs of callbacks already being in use. This issue is to discuss how we should handle having an example be used more than once. We could add a random id to the outputs, or some sort of prefix like page name. Let me know what you think!
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 by reproducing the failure when the same code example is loaded more than once with tools.load_example, then trace which callback outputs are reported as already in use. Compare possible namespacing based on a random ID or page name. Done means repeated example instances can coexist without callback-output ID collisions.
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
- 25/100