Skip to content

Commit

Permalink
Corrects Information (MicrosoftDocs#5480)
Browse files Browse the repository at this point in the history
  • Loading branch information
chasewilson authored Feb 24, 2020
1 parent 1697b8d commit e644ebd
Show file tree
Hide file tree
Showing 4 changed files with 60 additions and 17 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -190,9 +190,15 @@ $a
```

You can use this parameter to create a variable that contains only error
messages from specific commands. The `$Error` automatic variable contains error
messages from specific commands and does not affect the behavior of the
`$Error` automatic variable. The `$Error` automatic variable contains error
messages from all the commands in the session. You can use array notation, such
as `$a[0]` or `$error[1,2]` to refer to specific errors stored in the variables.
as `$a[0]` or `$error[1,2]` to refer to specific errors stored in the
variables.

> [!NOTE]
> The custom error variable contains all errors generated by the command,
> including errors from calls to nested functions or scripts.

#### InformationAction

Expand Down Expand Up @@ -252,6 +258,11 @@ parameter; if you don't add the **InformationAction** common parameter,
`$InformationPreference` preference variable. For more information about
`$InformationPreference`, see [about_Preference_Variables](./about_Preference_Variables.md).

> [!NOTE]
> The information variable contains all information messages generated by the
> command, including information messages from calls to nested functions or
> scripts.

```yaml
Type: String
Aliases: iv
Expand Down Expand Up @@ -516,9 +527,8 @@ specific commands. You can use array notation, such as `$a[0]` or `$warning[1,2]
to refer to specific warnings stored in the variable.

> [!NOTE]
> The **WarningVariable** parameter does not capture warnings from nested
> calls in functions or scripts.

> The warning variable contains all warnings generated by the command,
> including warnings from calls to nested functions or scripts.
### Risk Management Parameter Descriptions

#### WhatIf
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -190,9 +190,15 @@ $a
```

You can use this parameter to create a variable that contains only error
messages from specific commands. The `$Error` automatic variable contains error
messages from specific commands and does not affect the behavior of the
`$Error` automatic variable. The `$Error` automatic variable contains error
messages from all the commands in the session. You can use array notation, such
as `$a[0]` or `$error[1,2]` to refer to specific errors stored in the variables.
as `$a[0]` or `$error[1,2]` to refer to specific errors stored in the
variables.

> [!NOTE]
> The custom error variable contains all errors generated by the command,
> including errors from calls to nested functions or scripts.

#### InformationAction

Expand Down Expand Up @@ -252,6 +258,11 @@ parameter; if you don't add the **InformationAction** common parameter,
`$InformationPreference` preference variable. For more information about
`$InformationPreference`, see [about_Preference_Variables](./about_Preference_Variables.md).

> [!NOTE]
> The information variable contains all information messages generated by the
> command, including information messages from calls to nested functions or
> scripts.

```yaml
Type: String
Aliases: iv
Expand Down Expand Up @@ -516,8 +527,8 @@ specific commands. You can use array notation, such as `$a[0]` or `$warning[1,2]
to refer to specific warnings stored in the variable.

> [!NOTE]
> The **WarningVariable** parameter does not capture warnings from nested
> calls in functions or scripts.
> The warning variable contains all warnings generated by the command,
> including warnings from calls to nested functions or scripts.

### Risk Management Parameter Descriptions

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -190,9 +190,15 @@ $a
```

You can use this parameter to create a variable that contains only error
messages from specific commands. The `$Error` automatic variable contains error
messages from specific commands and does not affect the behavior of the
`$Error` automatic variable. The `$Error` automatic variable contains error
messages from all the commands in the session. You can use array notation, such
as `$a[0]` or `$error[1,2]` to refer to specific errors stored in the variables.
as `$a[0]` or `$error[1,2]` to refer to specific errors stored in the
variables.

> [!NOTE]
> The custom error variable contains all errors generated by the command,
> including errors from calls to nested functions or scripts.

#### InformationAction

Expand Down Expand Up @@ -252,6 +258,11 @@ parameter; if you don't add the **InformationAction** common parameter,
`$InformationPreference` preference variable. For more information about
`$InformationPreference`, see [about_Preference_Variables](./about_Preference_Variables.md).

> [!NOTE]
> The information variable contains all information messages generated by the
> command, including information messages from calls to nested functions or
> scripts.

```yaml
Type: String
Aliases: iv
Expand Down Expand Up @@ -516,8 +527,8 @@ specific commands. You can use array notation, such as `$a[0]` or `$warning[1,2]
to refer to specific warnings stored in the variable.

> [!NOTE]
> The **WarningVariable** parameter does not capture warnings from nested
> calls in functions or scripts.
> The warning variable contains all warnings generated by the command,
> including warnings from calls to nested functions or scripts.

### Risk Management Parameter Descriptions

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -190,9 +190,15 @@ $a
```

You can use this parameter to create a variable that contains only error
messages from specific commands. The `$Error` automatic variable contains error
messages from specific commands and does not affect the behavior of the
`$Error` automatic variable. The `$Error` automatic variable contains error
messages from all the commands in the session. You can use array notation, such
as `$a[0]` or `$error[1,2]` to refer to specific errors stored in the variables.
as `$a[0]` or `$error[1,2]` to refer to specific errors stored in the
variables.

> [!NOTE]
> The custom error variable contains all errors generated by the command,
> including errors from calls to nested functions or scripts.

#### InformationAction

Expand Down Expand Up @@ -252,6 +258,11 @@ parameter; if you don't add the **InformationAction** common parameter,
`$InformationPreference` preference variable. For more information about
`$InformationPreference`, see [about_Preference_Variables](./about_Preference_Variables.md).

> [!NOTE]
> The information variable contains all information messages generated by the
> command, including information messages from calls to nested functions or
> scripts.

```yaml
Type: String
Aliases: iv
Expand Down Expand Up @@ -516,8 +527,8 @@ specific commands. You can use array notation, such as `$a[0]` or `$warning[1,2]
to refer to specific warnings stored in the variable.

> [!NOTE]
> The **WarningVariable** parameter does not capture warnings from nested
> calls in functions or scripts.
> The warning variable contains all warnings generated by the command,
> including warnings from calls to nested functions or scripts.

### Risk Management Parameter Descriptions

Expand Down

0 comments on commit e644ebd

Please sign in to comment.