-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Parameter completion should work even when #requires fails #4549
Copy link
Copy link
Closed
Labels
In-PRIndicates that a PR is out for the issueIndicates that a PR is out for the issueResolution-No ActivityIssue has had no activity for 6 months or moreIssue has had no activity for 6 months or moreUsability(LEGACY) Helps filter issues that might be higher priority because they directly affect usability(LEGACY) Helps filter issues that might be higher priority because they directly affect usabilityWG-Interactive-IntelliSensetab completiontab completion
Metadata
Metadata
Assignees
Labels
In-PRIndicates that a PR is out for the issueIndicates that a PR is out for the issueResolution-No ActivityIssue has had no activity for 6 months or moreIssue has had no activity for 6 months or moreUsability(LEGACY) Helps filter issues that might be higher priority because they directly affect usability(LEGACY) Helps filter issues that might be higher priority because they directly affect usabilityWG-Interactive-IntelliSensetab completiontab completion
Steps to reproduce
In a non-elevated PowerShell, try to tab complete parameters to a script that looks like:
Expected behavior
Completion works. Note that the current behavior is slightly useful as an indicator that the script won't run even after finishing the command line, but it is poor behavior in an editor that probably isn't running elevated.
Actual behavior
Completion fails silently
Environment data