Remove the old fuzzy suggestion and fix the local script file name suggestion by daxian-dbw · Pull Request #25177 · PowerShell/PowerShell
@SteveL-MSFT the other built-in suggestion was already moved to the FeedbackProvider code path (GeneralCommandErrorFeedback)
| // See if target is actually an executable file in current directory. | |
| var localTarget = Path.Combine(".", target); | |
| var command = invocation.GetCommand( | |
| localTarget, | |
| CommandTypes.Application | CommandTypes.ExternalScript); | |
| if (command is not null) | |
| { | |
| return new FeedbackItem( | |
| StringUtil.Format(SuggestionStrings.Suggestion_CommandExistsInCurrentDirectory, target), | |
| new List<string> { localTarget }); | |
| } |
Currently we still go through the old suggestion when the FeedbackProvider exp feature is disabled. Once FeedbackProvider exp feature is considered ready to move to stable, we will remove the old suggestion completely.