Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
Discovered at #2972224: Add .cspell.json to automate spellchecking in Drupal core, and pointed by @xjm in https://www.drupal.org/project/drupal/issues/3122088#comment-13628724
+++ b/core/.cspell.json
@@ -0,0 +1,1288 @@
+ "Protectected",
Proposed resolution
@xjm: Protected.
As title and see the change record https://www.drupal.org/node/3122084 for how to work with cspell.
Remaining tasks
Pick out all applicable words from #2972224: Add .cspell.json to automate spellchecking in Drupal core and fix them.
User interface changes
API changes
Data model changes
Release notes snippet
Comment | File | Size | Author |
---|---|---|---|
#4 | Screenshot 2020-05-29 at 12.12.34 AM.png | 169.35 KB | mohrerao |
#3 | 3138786-3.patch | 1.46 KB | sja112 |
Comments
Comment #2
sja112 CreditAttribution: sja112 at Srijan | A Material+ Company for Drupal India Association commentedComment #3
sja112 CreditAttribution: sja112 at Srijan | A Material+ Company for Drupal India Association commentedComment #4
mohrerao CreditAttribution: mohrerao as a volunteer and at Srijan | A Material+ Company for Drupal India Association commentedChecked for occurrence of 'Protectected' after applying 3138786-3.patch and found none.
Moving to RTBC
Comment #9
xjmNice. In this case it was an actual misspelling of a variable name. (In a string message, but still a helpful improvement.)
Thanks @mohrerao for reviewing. In addition to pasting the CLI output directly next time, I'd also suggest using
grep -ri
in case there are other places where the same typo has a different casing.I looked in the actual test to verify the change here and make sure it was backportable, since this is a weirdly long message for a test assertion. It appears that it's being used here within a custom assertion, and so that's why the message is so long. Since it's fixing the message output of the test, I think it's a patch-eligible bugfix. So, I committed this to 9.1.x, and cherry-picked it to 9.0.x, 8.9.x, and 8.8.x. Thanks!