- Notifications
You must be signed in to change notification settings - Fork7.7k
[release/v7.5] Remove the old fuzzy suggestion and fix the local script file name suggestion#25330
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Conversation
We received report for this issue in Stack Overflow and Steven also received the report from other channels. It was a regression in 7.4, but the "FuzzyCommand" was under an experimental feature in 7.4, so users won't notice it's broken unless they turn on the feature. |
/azp run PowerShell-CI-linux-packaging, PowerShell-Windows-Packaging-CI |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
3ad6242
intoPowerShell:release/v7.5Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Backport of#25177 to release/v7.5
Triggered by@TravisEz13 on behalf of@daxian-dbw
Original CL Label: CL-General
/cc @PowerShell/powershell-maintainers
Impact
Choose either tooling or Customer impact.
Tooling Impact
Customer Impact
It was a regression in 7.4, but the "FuzzyCommand" was under an experimental feature in 7.4, so users won't notice it's broken unless they turn on the feature.
However, in 7.5, the "FuzzyCommand" feature was made stable, so users start to see this issue.
Regression
stopped working in 7.5
Testing
We don't think this is testable
Manually tested
Risk
[High/Medium/Low. Justify the indication by mentioning how risks were measured and addressed.]