- Merge request !65#3546285: Include navigation events in undo/redo → (Closed) created by Unnamed author
- Merge request !141#3546285: Account for route changes in undo/redo stack → (Merged) created by Unnamed author
Include navigation changes in the undo history, so users can undo/redo their actions by switching to the route where those actions occurred. This will enable us to expand the undo history to the code editor, and to present a unified undo history.
Currently undo/redo covers two RTK slices: layoutModel and pageData. They are both wrapped with the undoable() reducer enhancer by redux-undo, which means they both track their own history. To present a single, linear timeline to the user, uiSlice maintains an undoStack to track which which slice's state needs to be changed.
Introduce a new navigationSlice to track the current route, and enhance it with redux-undo to build a history. Synchronize route changes between the store and the actual routing. Cover navigationSlice in the uiSlice's undoStack.
The undo/redo buttons and keyboard shortcuts can trigger navigation.
Active
1.0
Page builder
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.