fix: pluralizations of the verb "to have" across the repository #573
Conversation
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
dippydocus
approved these changes
Nov 25, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When deleting multiple resources, we're pluralizing the resource type in case multiple resources were deleted at the same time, so that the CLI displays the correct word to the user.
However, the rest of the phrases were not being pluralized correctly.
This fixes it by internalizing the dependency on
github.com/alejandrojnm/go-pluralizeand extending it by adding a utilitypluralize.Hasfunction that usespluralize.Pluralizeto correctly display "has" or "have" depending on the size argument passed in.This new utility has been added to all cases where this problem could be found (mostly when deleting multiple resources at once).