Add built-in PowerShell shell completion support#3637
Open
doctorlai-msrc wants to merge 2 commits into
Open
Conversation
This file contains hidden or 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
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.
Summary
Adds
PowerShellCompleteas a fourth built-in shell completer, alongside theexisting
BashComplete,ZshComplete, andFishComplete. Users of Click-basedCLIs on Windows PowerShell 5.1+ or PowerShell (pwsh) 7+ can now opt into TAB
completion the same way they do for the other shells:
…or generate the script once and source it:
PowerShell support has been a long-standing gap in Click; downstream projects
have repeatedly worked around it by shipping ad-hoc completer scripts. This PR
makes it a first-class built-in so every Click-based CLI gets it for free.