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

Config key cketoolbar vs toolbar? #113

Closed
quicksketch opened this issue Dec 4, 2023 · 5 comments · Fixed by #114 or #123
Closed

Config key cketoolbar vs toolbar? #113

quicksketch opened this issue Dec 4, 2023 · 5 comments · Fixed by #114 or #123

Comments

@quicksketch
Copy link
Member

At some point the config key and form element for the toolbar was changed from toolbar to cketoolbar. This is unnecessary prefixing, since the settings are exclusive to the ckeditor5 editor. It'll probably show up in core's cSpell as an invalid word too. Should we change it back?

@indigoxela
Copy link
Member

indigoxela commented Dec 5, 2023

This is unnecessary prefixing, since the settings are exclusive to the ckeditor5 editor.

In fact, this change was essential to get things working. Reverting isn't possible without changes in core.

See also backdrop/backdrop-issues#6203

This filter quirk not only affects CK5, but any other editor with such a setting in the filter form. If an implementation uses "toolbar", then things will break because of different variable structure for the editors.

@indigoxela
Copy link
Member

A little off topic: I don't think, cspell should dictate the names of variables. Nice and speaking names, OK, but not being able to use (proper) variables names because of a spellchecker... 🤪

@quicksketch
Copy link
Member Author

I'd like to put this config key back to just "toolbar", but you're right that we can't do this easily while there's the core bug. I filed a PR at #114 but it's blocked until backdrop/backdrop-issues#6203 is fixed and we have another bug-fix release (1.26.3).

@quicksketch
Copy link
Member Author

I merged the PR at #114, but @indigoxela pointed out some pretty serious flaws in the update hook as part of the core code review. I should have retested this again before merging. I filed a follow-up PR at #123 that fixes our new test coverage and corrects the update hook to save the new config values.

@quicksketch
Copy link
Member Author

Also #123 fixed our test runs by checking out Backdrop 1.26.x instead of 1.x, because this contrib module conflicts with the new core module.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants