-
Notifications
You must be signed in to change notification settings - Fork 8.1k
Correct casing for automatic variables #11568
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.
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
Correct casing for automatic variables #11568
Conversation
|
This is a large number of files changed. Would be easier to review if you can change one variable per commit. |
|
@SteveL-MSFT OK, I will rewrite |
698aed5 to
090ad9c
Compare
test/powershell/Language/Classes/Scripting.Classes.BasicParsing.Tests.ps1
Show resolved
Hide resolved
test/powershell/Language/Classes/Scripting.Classes.BasicParsing.Tests.ps1
Show resolved
Hide resolved
test/powershell/Language/Classes/Scripting.Classes.BasicParsing.Tests.ps1
Show resolved
Hide resolved
|
CodeFactor issues are preexisting |
|
@iSazonov why not a squash merge? |
|
@iSazonov Yes please use squash commits. I've remove permissions for merge commits. |
|
GitHub did return an error after I press |
|
Opened issue PowerShell/PSScriptAnalyzer#1401 to detect regressions. |
|
🎉 Handy links: |
PR Summary
Correct casing for special variables (a.k.a. automatic variables)
PR Context
The following code was used to generate a list of special variables:
PR Checklist
.h,.cpp,.cs,.ps1and.psm1files have the correct copyright headerWIP:or[ WIP ]to the beginning of the title (theWIPbot will keep its status check atPendingwhile the prefix is present) and remove the prefix when the PR is ready.