Fix autosave functionality and dirty state logic #449
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request
This PR addresses critical issues with the editor's data persistence and state management. It fixes a bug where autosave was failing to trigger and corrects the
dirty statelogic to accurately reflect unsaved changes, ensuring the indicator clears when content matches the saved version.Description
onChangecallback was not being called in theEditorBufferStoreto include asavedContentfield for each buffer.updateBufferContentandmarkBufferDirtyto usesavedContentfor accurate dirty state calculation. This resolves the issue where the dirty indicator would remain active even after reverting changes to the original state.onChangeis correctly propagated fromuseEditorStateStoreto theEditorScreenshots/Videos
Related Issues
Closes # Fixes #