Core: provide a Editor creation factory

[fredck]

Before proposing anything, let me illustrate the two cases I've faced recently, which motivated this issue.

Case 1

While working on ckeditor/ckeditor5-markdown-gfm#30, I've noticed that, although the plugin is setting editor.data.processor to the GFM data processor, the editor classes (classic, inline, etc.) are in any case pointlessly (at that point) setting that same property to the HTML data processor (which later on is overwritten by the plugin).

I figured that it would be safe to set the data processor only after initing all plugins, if no plugin set it. Then, I've also figured that this would involve touching all four official editor classes, basically deleting and pasting the same lines, in the same places. It would not fix other editors out there though.

Case 2

While coding a custom editor class, it is depressing the amount of copy/paste that has do be done. One does it without even thinking why, copying the boilerplate from the relative documentation guide.

All that sounded overcomplicated and pointless. I see this as a weak part of the API.

Proposal

The creation of a factory that will remove most of the boilerplate from the editor classes and centralize it in a single place.

---

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

[CKEditorBot]

There has been no activity on this issue for the past year. We've marked it as stale and will close it in 30 days. We understand it may be relevant, so if you're interested in the solution, leave a comment or reaction under this issue.

[CKEditorBot]

We've closed your issue due to inactivity over the last year. We understand that the issue may still be relevant. If so, feel free to open a new one (and link this issue to it).