Problem/Motivation
Queuing/Queueing is a very fun word, and has two correct spellings, neither of which is associated with typical US/UK conventions, they're just, both correct (i.e. there's no existing spelling standard that dictates which spelling we should be using in Drupal).
Should we set a "correct spelling" for the Drupal ecosystem, in cspell/dictionary.txt?
https://english.stackexchange.com/questions/60852/queueing-or-queuing
Proposed resolution
I strongly recommend "queueing" because, oh my god, five consecutive vowels is definitely the correct answer.
1) Change flagwords in cspell.json to include queuing
"flagWords": [
"e-mail",
"grey",
"hte",
"ist",
"please",
"queuing"
],
2) yarn run -s spellcheck:core --no-must-find-files --no-progress
3) Fix any occurrences found.
Remaining tasks
Drupal is to use queueing.
User interface changes
API changes
Data model changes
Release notes snippet
| Comment | File | Size | Author |
|---|---|---|---|
| #23 | Screenshot 2024-02-11 at 11.12.14.png | 39.7 KB | bramdriesen |
Issue fork drupal-3364292
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:
- 3364292-spelling-queueing
changes, plain diff MR !6536
Comments
Comment #2
alisonComment #3
cilefen commented+1 for "queueing", same reasons.
Comment #4
quietone commentedComment #5
quietone commentedThat was meant to be the parent, not related
Comment #6
_utsavsharma commentedAdded queueing to dictionary.txt and changed its occurrence in the remaining files.
Comment #7
quietone commented@_utsavsharma, thank you for your interest in spelling issue. Before uploading a patch it is good practice to make sure that it applies locally. Also, spelling issues often require the rebuilding of the dictionary so I recommend reading the parent issue of this one. Cheers!
I am setting this to active because we need to decide which spelling or spellings we want to use in Drupal before patching. Also, this patch is adding a word to the Drupal dictionary which already existing in the en_us dictionary.
Comment #8
pragati_kanade commentedAbove Patch looks good to me. All "queuing" replace with recommended spell "queueing".
Comment #9
pragati_kanade commentedComment #10
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue.
While you are making the above changes, we recommend that you convert this patch to a merge request. Merge requests are preferred over patches. Be sure to hide the old patch files as well. (Converting an issue to a merge request without other contributions to the issue will not receive credit.)
Comment #11
quietone commented@pragati_kanade, the previous comment set this issue to Active because there has not really been enough discussion on the choice of spelling.
Comment #12
dww+1 to "queueing" as the "correct" spelling, even though there's some indication that that's the "British" way of spelling it, while the version with 1 'e' is more "American".
British
https://www.oed.com/dictionary/queueing_adj
American
https://www.collinsdictionary.com/us/dictionary/english/queuing
https://www.merriam-webster.com/dictionary/queuing
Yet every one of those pages list both versions as correct. So it seems very subjective.
So I think the bikeshed should be painted "queueing". 😂
Cheers,
-Derek
Comment #13
urvashi_vora commented+1 for "Queueing", although both the spellings mean the same but going with the longer one.
Comment #14
bramdriesenHaha 😂
Queue + ingSeems the most logical for me as well. That's how I, as a non native English speaking person would write it.Comment #15
jonathan1055 commented+1 for the full longer version queueing
That is a good point, thanks.
Six people here agree with the longer version and no-one has wanted the shorter version. So that seems like we have reached an agreement.
Comment #16
quietone commentedThanks everyone!
Comment #18
bramdriesenUpdated patch to MR (and rebased). Also reverted the change in the core/vendor directory as I'm not sure we should be changing that.
Comment #19
bramdriesenSpellcheck output.
Comment #20
bramdriesenJust realised the patch is not how it should be fixed. My bad. Will update to what is suggested in the IS.
Comment #21
bramdriesenUpdated to the correct implementation.
New cspell output.
Comment #22
dwwGitLab CI won't really understand what "test-only" means here. 😂 So I just applied the change to the
flagWordsincore/.cspell.jsonand ranyarn run -s spellcheck:core. The only error I got was:So flagWords is working as expected. The full pipeline is green, since that is fixed here in the MR.
The summary is clear and complete. I'm updating the title to try to be more appropriate for a commit message.
The MR is all good. This is ready.
Thanks!
-Derek
Comment #23
bramdriesenThere is a test only run that you can trigger in GitLab CI 😉 I believe this is a run without the code changes and only test changes. But that doesn't help in this case
Comment #24
dwwIndeed, I’m very familiar with that job and how it works. I’m helping to get it ported into the contrib templates. #3418831: Test-only job. That’s why I said it would not help for this issue and why I did a “test-only” approach manually to make it easier for committers. 👍
Comment #27
quietone commentedCommitted c574a6e and pushed to 11.x. Cherry picked to 10.2.x to keep dictionary in sync and there are no code changes here.
Thanks!