'use_form' is not a supported key while migrating from CKEditor 4 to 5

I'm experiencing this issue also over a site I'm working on right now, but The site was already working with CKeditor5 since long time ago, the issue started to happen when upgrade to drupal 10.3

I can confirm this with Drupal 10.3.0!

It's a schema issue. Here's a good fix from token_filter module: 🐛 'replace_empty' is not a supported key. Fixed

@Grevil would you be so kind? :)

I tried to fix it properly in 3456700-useform-is-not, but that is quite the rabbit hole and my current approach is still not the best.

Basically, the problem is that our details wrapper "use_form" is seen as a valid setting and saved. Instead it shouldn't be saved at all, or atleast it should be seen as a sub-mapping of the settings mapping, but doing so will result in other problems.

Let's merge the quick fix for now, so this module can be used again, but keep the issue open, so once we have the time, we can continue our work in 3456700-useform-is-not.

Thanks for the quickfix @Grevil!
I'd suggest we merge this to make the text format form savable again, but then leave this open for a clean fix in the future?

Thanks for the fix @Grevil! RTBC!

Setting this fixed to reopen the issue for a final solution, see #7

Setting this back to active for a final solution, see #7. Ideas welcome!

Best would be to get the "details" wrapper out of the data! (TBH I think that's the only real solution).

Best would be to get the "details" wrapper out of the data!

That's what the module is actually already doing in "validateSettingsForm", I am unsure based on what exactly the "'use_form' is not a supported key." text is displayed, can't be based on the saved values, as there shouldn't be a value for "use_form" saved.

But yea. Still unsure how to approach this.

Tagged 3.1.7 with the quickfix!