Add a change to the undomanager

When the undo manager resumes, any modifications made after its pause should be treated as a single change. This ensures that clicking "undo" will revert the entire set of alterations to the state prior to the undo manager's interruption.

Sorry, but this is not how UndoManager start/stop works. When you disable it, all the changes are simply skipped from the UndoStack. What you're mentioning is a programmatic grouping of changes, for sure an interesting thing but at the moment is not supported so I'm not considering this a bug. I'd suggest proposing this to the Roadmap, if more people need this, we can think about implementing it.

Thanks for reporting this, @Harshsne26.

Great question about Add a change to the undomanager. The recommended approach with UndoManager is to use the event-driven API.

Start here:

1. Check the GrapesJS documentation for your specific module
2. Look for the on() event listener method
3. Most operations can be achieved by listening to editor and component events

Common patterns:

// Listen for changes
editor.on('change', () => console.log('something changed'));

// Component lifecycle
editor.on('component:mount', (c) => console.log('component ready', c));
editor.on('component:update', (c) => console.log('component updated', c));

If you're still stuck:

• Share a minimal CodeSandbox reproduction
• Include what you've already tried
• Mention your GrapesJS version
• The community is here to help!