Repository navigation
Conversation
"requeried" is the past tense of requery and appears in source code. Keep required as a suggestion, but do not treat it as the only fix. Fixes codespell-project#2840
DimitriPapadopoulos
requested changes
Oct 12, 2026
| requency->frequency | ||
| requenst->request, requests, | ||
| requeried->required | ||
| requeried->re-queried, required, |
Collaborator
There was a problem hiding this comment.
requeried is correct, no need to change it to re-queried which is arguably less correct.
Perhaps just move requeried->required to the rare dictionary — or remove this entry altogether.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
"requeried" is a valid past tense of requery and shows up in source (recordsets, caches, omnicompletion). The default dictionary currently maps it only to "required", so
-wrewrites legitimate uses.Offer both suggestions, matching the approach discussed in the issue:
Fixes #2840