Problem/Motivation
CKEditor 4 will be removed from core in Drupal 10.
The Inline Form Errors module has test coverage to ensure it works well with both CKEditor 4 and CKEditor 5:
Drupal\Tests\inline_form_errors\FunctionalJavascript\FormErrorHandlerCKEditorTestDrupal\Tests\inline_form_errors\FunctionalJavascript\FormErrorHandlerCKEditor5Test
There does not appear to be an integration code inside Inline Form Errors itself (no references to ckeditor, case-insensitive, outside the two tests).
Proposed resolution
Move the CKEditor 4 test coverage to the ckeditor namespace.
Leave Drupal\Tests\inline_form_errors\FunctionalJavascript\FormErrorHandlerCKEditor5Test in place for testing CKEditor 5 integration.
Remaining tasks
TBD
User interface changes
N/A
API changes
N/A
Data model changes
N/A
Release notes snippet
N/A
Issue fork drupal-3271046
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
xjmComment #4
xjmComment #5
longwaveGiven we are changing the namespace from IFE to CKEditor, should we remove CKEditor from the test class name and change it to something like InlineFormErrorsTest?
Comment #6
xjm@longwave Personally I think it's fine as-is; the name already included reference to both modules. I always find that easier to understand anyway.
Comment #7
danflanagan8Stumbled upon this issue as I was preparing to update inline_form_errors as part of the classy-to-stark meta. I thought maybe there'd be some issue about
FormErrorHandlerCKEditorTestand here we are! This appears to be the only test ininline_form_errorsthat would need to be fixed. So this move kills two birds with one stone!Confirmed that ckeditor is not mentioned outside the two tests mentioned. Looks good to me.
Comment #8
catchCommitted/pushed to 10.0.x and cherry-picked to 9.4.x, thanks!
Comment #10
xjmFixing status from bot crosspost or whatnot.