-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
(GH-11248) Clarify behavior for Register-ArgumentCompleter
parameters
#11249
Merged
sdwheeler
merged 2 commits into
MicrosoftDocs:main
from
michaeltlombardi:ab-281953/main/argument-completer-behavior
Jul 10, 2024
Merged
(GH-11248) Clarify behavior for Register-ArgumentCompleter
parameters
#11249
sdwheeler
merged 2 commits into
MicrosoftDocs:main
from
michaeltlombardi:ab-281953/main/argument-completer-behavior
Jul 10, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Learn Build status updates of commit 2f9a014: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
🙏 |
…ter` parameters Prior to this change, the `Register-ArgumentCompleter` reference didn't indicate that specifying the **CommandName** parameter without the **ParameterName** or **Native** parameters causes the command to behave as if the user specified the `-Native` switch. This change: - Clarifies that users should always specify the **ParameterName** parameter when registering an argument completer for a PowerShell command. - Resolves MicrosoftDocs#11248 - Fixes AB#281953
michaeltlombardi
force-pushed
the
ab-281953/main/argument-completer-behavior
branch
from
July 10, 2024 20:24
2f9a014
to
9d10a7a
Compare
Learn Build status updates of commit 9d10a7a: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
This change adds further clarification to various sections of the reference documentation for `Register-ArgumentCompleter`. It also addresses some style and formatting issues.
Learn Build status updates of commit ce7ccab: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
sdwheeler
approved these changes
Jul 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Summary
Prior to this change, the
Register-ArgumentCompleter
reference didn't indicate that specifying the CommandName parameter without the ParameterName or Native parameters causes the command to behave as if the user specified the-Native
switch.This change:
-ParameterName
argument implies the-Native
switch #11248PR Checklist