-
Notifications
You must be signed in to change notification settings - Fork 513
Expand aliases works silently, needs 'running indicator' #208
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Thanks Sergei! |
Wow, that worked?! :-) |
With ScriptAnalyzer providing the ability to expand aliases through its SuggestCorrections property, the question I would like to ask is, should we have "expand aliases" have and maintain it's own implementation or use ScriptAnalzyer''s service? |
Script Analyzer's expansion is nice when the user wants to expand a single alias into the fully-qualified command name. Doug's Expand Alias command does it automatically across the whole file, so I think the intent is a little different. However, if we want to provide this type of "whole-file correction" operation in Script Analyzer we can definitely discuss how to make that happen. |
It would be cool if this could do like: "50 alias expanded" though a simple "Aliases expanded" would be a good first step. |
The running indicator I added in #1227 seems to work for this. Closing |
Great! |
When I worked on PowerShell/platyPS#126
I tried use "Expand aliases" on a file with 1.5k lines.
There was no feedback from vscode that it started to do something.
I thought it's not working, but then I checked it in 20 seconds and it was done.
I'm not sure how much time did it take, but since the operation is not instant it requires some visual progress indication for better UX.
It could be applicable to other refactorings as well.
The text was updated successfully, but these errors were encountered: