Spotted a language issue in #Drupal's new #CKEditor5, set about on a fix, surprised at a lack of "non-standard language" support.

Got a partial solution together, learnt of changes in testing and mocking along way, when writing up & linking prior work found open issue I missed searching ... 🫢

Felt dumb but two good things, learning a bit more about testing plugins and mocking interfaces, & my implementation looks very similar to the existing, reassuring that I was on a sensible path.

@danielsiepmann I have discussed this several times with my colleagues and everyone agrees that plugin development for #CKEditor5 is hell.

I don't know why #TYPO3 decided to keep using #CkEditor5, because I don't see any benefit. It seems very over-engineered (it has its own debug console!) and all plugins from #CkEditor4 have to be completely rebuilt as there is no upgrade path. So it wouldn't matter if #TYPO3 had switched to another #RTE.

Would love to see #tiptap or #tinymce in #TYPO3.

#CKEditor5 in #Drupal looks nice... until you want to build a plugin with more than a simple input text field.

I wish I am wrong and there is an easy way out-of-the-box... but it is a huge step back from a developer perspective when you cannot "easily" embed Drupal Form (aka Dialogs).

I am amazed this breaking change did not ring alarms
when it was released in 2021! 😩

Orignial announcement:
https://www.drupal.org/project/drupal/issues/3231364

A discussion between developers about limitations:
https://drupal.slack.com/archives/C01GWN3QYJD/p1680720611943089