Skip to content

Documentation corrections for AvoidUsingPositionalParameters #1917

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 1 commit into from
Aug 18, 2023
Merged

Documentation corrections for AvoidUsingPositionalParameters #1917

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
corrections in AvoidUsingPositionalParameters.md
  • Loading branch information
@God-damnit-all
God-damnit-all authored May 23, 2023
commit f9f9ea6467cdb39afc995e0520f8c589043033e6
4 changes: 2 additions & 2 deletions docs/Rules/AvoidUsingPositionalParameters.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ supplied. A simple example where the risk of using positional parameters is negl

```powershell
Rules = @{
AvoidUsingPositionalParameters = @{
PSAvoidUsingPositionalParameters = @{
CommandAllowList = 'az', 'Join-Path'
Enable = $true
}
Expand All @@ -33,7 +33,7 @@ Rules = @{

### Parameters

#### AvoidUsingPositionalParameters: string[] (Default value is 'az')
#### CommandAllowList: string[] (Default value is 'az')

Commands to be excluded from this rule. `az` is excluded by default because starting with version 2.40.0 the entrypoint of the AZ CLI became an `az.ps1` script but this script does not have any named parameters and just passes them on using `$args` as is to the Python process that it starts, therefore it is still a CLI and not a PowerShell command.

Expand Down