-
Notifications
You must be signed in to change notification settings - Fork 3.3k
History: withNewBatch #5747
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
History: withNewBatch #5747
Conversation
🦋 Changeset detectedLatest commit: cfb0296 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
dylans
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks fine. It would be good to add something to the docs as well, but that can happen in a separate PR.
…e(inspired by slate) ref: ianstormtaylor/slate#5747
|
@zbeyens thank you for your work, I have apply the idea to my drawing framework project |
* feat * Create gold-cheetahs-rest.md * refactor * fix
…e(inspired by slate) (#996) ref: ianstormtaylor/slate#5747
* feat * Create gold-cheetahs-rest.md * refactor * fix
Description
Add a new method
withNewBatchtoHistoryEditor. This method allows users to explicitly start a new batch in the history for the first operation, while merging subsequent operations as usual. This provides more fine-grained control over history management, particularly useful for complex editing operations that should be treated as a single unit in the undo/redo history.Example
Checks
yarn test.yarn lint. (Fix errors withyarn fix.)yarn start.)yarn changeset add.)Disclaimer: AI generated