Skip to content

Correct casing of parameters as well in PSUseCorrectCasing formatter rule #1391

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bergmeister merged 4 commits into from
Jan 16, 2020
Merged

Correct casing of parameters as well in PSUseCorrectCasing formatter rule #1391

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
df751f8
Correct casing of parameters. TODO: diagnostic messages
Jan 4, 2020
4686bb9
Update message strings
Jan 4, 2020
d16eba5
update docs
Jan 5, 2020
fee5933
Merge branch 'master' of https://github.com/powershell/psscriptanalyz…
Jan 16, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update message strings
  • Loading branch information
Christoph Bergmeister committed Jan 4, 2020
commit 4686bb92fd8ec3e13fff390487bdfdbd4205c20f
86 changes: 39 additions & 47 deletions Rules/Strings.Designer.cs
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

8 changes: 4 additions & 4 deletions Rules/Strings.resx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1081,13 +1081,13 @@
<value>Use space before pipe.</value>
</data>
<data name="UseCorrectCasingCommonName" xml:space="preserve">
<value>Use exact casing of cmdlet/function name.</value>
<value>Use exact casing of cmdlet/function/parameter name.</value>
</data>
<data name="UseCorrectCasingDescription" xml:space="preserve">
<value>For better readability and consistency, use the exact casing of the cmdlet/function.</value>
<value>For better readability and consistency, use the exact casing of the cmdlet/function/parameter.</value>
</data>
<data name="UseCorrectCasingError" xml:space="preserve">
<value>Cmdlet/Function does not match its exact casing '{0}'.</value>
<value>Cmdlet/Function/Parameter does not match its exact casing '{0}'.</value>
</data>
<data name="UseCorrectCasingName" xml:space="preserve">
<value>UseCorrectCasing</value>
Expand All @@ -1104,4 +1104,4 @@
<data name="UseProcessBlockForPipelineCommandName" xml:space="preserve">
<value>UseProcessBlockForPipelineCommand</value>
</data>
</root>
</root>