Limit history when `show_undo_redo=False`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 24.4k
- Forks
- 2.3k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 13
Description
After #724 and https://github.com/plotly/dash-renderer/pull/175, the state history is only relevant to revert, which is used for error recovery so only needs to hold one previous (good) state as described in https://github.com/plotly/dash-renderer/pull/175#discussion_r285819165. If we simplify the history when the undo/redo toolbar is hidden, we may see a significant performance boost for large and/or frequently-updated apps.
Possibly related: #699, #707
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 reading #724 and the dash-renderer pull request #175, especially the linked discussion, then review related issues #699 and #707. Trace how history supports revert when show_undo_redo is false; done means retaining the needed recovery state while avoiding unnecessary history and demonstrating the performance improvement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100