Skip to content
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

[ckeditor5-inspector] Add history/operations/batch tab #6104

Closed
rshipp opened this issue Jan 21, 2020 · 4 comments
Closed

[ckeditor5-inspector] Add history/operations/batch tab #6104

rshipp opened this issue Jan 21, 2020 · 4 comments
Labels
type:feature This issue reports a feature request (an idea for a new functionality or a missing option).

Comments

@rshipp
Copy link
Contributor

rshipp commented Jan 21, 2020

📝 Provide a description of the new feature

Display the history stack, and some way to look at batches/operations and have a basic understanding of what they're doing (e.g. InsertOperation on path [1, 0, 0, 1]). I know undo/redo is an optional plugin, so I'm not sure if this'd be in-scope for the inspector, but it'd be super helpful for me.

My use cases:

  1. I have a bunch of custom components, and I've noticed some of them seem to be breaking undo/redo functionality. When I insert them via a Command, then try to undo, they aren't removed from the editor. I'm going to have to debug why, and it'd be convenient to have an easier way to explore the history / undo batches than clicking through things in the console.

  2. I'm building some persistent undo/redo functionality, where undo batches and operations are stored to a server and manually loaded back into the editor on pageload. This also has me debugging a bunch of batch/operation stuff manually from the console.


If you'd like to see this feature implemented, add a 👍 reaction to this post.

@rshipp rshipp added the type:feature This issue reports a feature request (an idea for a new functionality or a missing option). label Jan 21, 2020
@ma2ciek
Copy link
Contributor

ma2ciek commented Jan 22, 2020

cc @oleq

@oleq
Copy link
Member

oleq commented Jan 23, 2020

Hi, @rshipp!

Thank for your suggestions. That would definitely help a lot of people figure out some operation mess in their projects. I can't give you an ETA because there is plenty of other improvements already on our TODO list but I promise I'll keep it in the back of my head 😀

@oleq
Copy link
Member

oleq commented Jan 23, 2020

Oh, BTW, since you're here, can I ask you to skim through existing issues and give 👍where it makes sense for you? That would help us a lot in the future.

@oleq
Copy link
Member

oleq commented Jan 23, 2020

Issue moved to ckeditor/ckeditor5-inspector #70 via ZenHub

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:feature This issue reports a feature request (an idea for a new functionality or a missing option).
Projects
None yet
Development

No branches or pull requests

3 participants