Skip to content
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

6/11/2024 PM Publish #11182

Merged
merged 2 commits into from
Jun 11, 2024
Merged

6/11/2024 PM Publish #11182

merged 2 commits into from
Jun 11, 2024

Conversation

Taojunshen
Copy link
Contributor

@Taojunshen Taojunshen commented Jun 11, 2024

Prior to this change, the article 'Everything you wanted to know about $null' used the term 'empty $null' to describe
[System.Management.Automation.Internal.AutomationNull]::Value

However, this terminology isn't clear enough, as both that value and the $null value itself can be considered to be 'empty.'

This change:

PR Summary

PR Checklist

  • Descriptive Title: This PR's title is a synopsis of the changes it proposes.
  • Summary: This PR's summary describes the scope and intent of the change.
  • Contributor's Guide: I have read the contributors guide.
  • Style: This PR adheres to the style guide.

Prior to this change, the article 'Everything you wanted to know about `$null`'
used the term 'empty `$null`' to describe
`[System.Management.Automation.Internal.AutomationNull]::Value`

However, this terminology isn't clear enough, as both that value and the `$null`
value itself can be considered to be 'empty.'

This change:

- Updates to use the terminology 'enumerable null' instead of 'empty `$null`'
  to describe the value.
- Resolves #11175
- Fixes AB#260888
Copy link
Contributor

Learn Build status updates of commit 6d5d3c5:

✅ Validation status: passed

File Status Preview URL Details
reference/docs-conceptual/learn/deep-dives/everything-about-null.md ✅Succeeded View (>=powershell-5.1)

For more details, please refer to the build report.

For any questions, please:

…11180)

Prior to this change, the example description in the article
_How to validate an argument using a script_ declared that
the example validates that the input belongs to a set of
possible values. That description belongs to a different
example, using `[ValidateSet()]`.

This change:

- Corrects the example description to match the code.
- Fixes AB#263705
Copy link
Contributor

Learn Build status updates of commit 9288d35:

✅ Validation status: passed

File Status Preview URL Details
reference/docs-conceptual/developer/cmdlet/how-to-validate-an-argument-using-script.md ✅Succeeded View (>=powershell-5.1)
reference/docs-conceptual/learn/deep-dives/everything-about-null.md ✅Succeeded View (>=powershell-5.1)

For more details, please refer to the build report.

For any questions, please:

@Taojunshen Taojunshen merged commit df5a87d into live Jun 11, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants