Update docs and diagnostic message for UseCorrectCasing #2138
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
…l sites It made it cumbersome to pass a different number of arguments to the string.Format call and didn't seem necessary
…ameters, and operators
liamjpeters
requested review from
andyleejordan,
bergmeister,
michaeltlombardi and
sdwheeler
as code owners
liamjpeters
commented
Oct 31, 2025
|
|
||
| ## How | ||
|
|
||
| - Use exact casing for type names. |
Contributor
Author
There was a problem hiding this comment.
I can't see anything in the rule which acts on type names
sdwheeler
approved these changes
Dec 2, 2025
Collaborator
sdwheeler
left a comment
sdwheeler
left a comment
There was a problem hiding this comment.
Docs changes look good to me.
bergmeister
approved these changes
Dec 2, 2025
Collaborator
bergmeister
left a comment
bergmeister
left a comment
There was a problem hiding this comment.
LGTM. Thanks, will go through your other PRs the next days. Sorry it's taken so long
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
PR Summary
Fixes a small regression from #1704 where incorrectly cased parameters are reported as Functions/Cmdlets. i.e.
Resulted in a diagnostic message of:
Function/Cmdlet '-name' does not match its exact casing 'Name'.instead of:
Parameter '-name' of function/cmdlet 'Get-Process' does not match its exact casing 'Name'.Added some tests for the messages.
Small tweaks to rule docs too, including that the descriptions of
CheckCommandsandCheckOperatorwere transposed.Closes #2136
PR Checklist
.cs,.ps1and.psm1files have the correct copyright headerWIP:to the beginning of the title and remove the prefix when the PR is ready.