-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Feedback provider for legacy usage #19524
Copy link
Copy link
Closed
Labels
Issue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bugNeeds-TriageThe issue is new and needs to be triaged by a work group.The issue is new and needs to be triaged by a work group.Resolution-No ActivityIssue has had no activity for 6 months or moreIssue has had no activity for 6 months or more
Metadata
Metadata
Assignees
Labels
Issue-Enhancementthe issue is more of a feature request than a bugthe issue is more of a feature request than a bugNeeds-TriageThe issue is new and needs to be triaged by a work group.The issue is new and needs to be triaged by a work group.Resolution-No ActivityIssue has had no activity for 6 months or moreIssue has had no activity for 6 months or more
Type
Projects
Status
Feedback Provider Requests
Summary of the new feature / enhancement
Users switching from cmd or bash may have muscle memory for commonly used commands with parameters. It would be useful to have a FeedbackProvider detect this and inform the user what the correct PowerShell syntax would be and have a predictor so that it can fill in the suggested fix.
Common use cases:
rm -rf
dir /s/q
Please add your own to this issue.
To clarify, as it seems some folks misunderstood the intent of this issue, the idea here is to leverage the Feedback provider model we added in PowerShell 7.4, so that if you were to type:
rm -rfIt would fail like it does today, but as part of the response, you would get something like:
In this case, trying to keep the explanation text short and also using short hand since this is interactive only.