Repository navigation
Component undo/redo replay example for headless consumers #6850
PerchAnton
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I put together a small external example for applications that use GrapesJS headlessly: code, native control, and three JSON traces.
It runs GrapesJS 0.23.8 and checks component renaming, an unchanged value after undo, and replacing a redo branch with a new edit. It deliberately calls
undo(false)/redo(false)for individual entries; the default grouped behavior is not treated as a bug. The three traces cover 15 steps and pass on Windows and Linux.The runner is my project, interaction-check. Its role here is to package a sequence and a step-level state report; it does not replace GrapesJS tests or require a runtime dependency. Would this be useful as an optional community testing example, or is there an existing guide where this fits better? The implementation and validation were AI-assisted with Codex.
All reactions