We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Yes, it can be a little confusing that there are two refactor options available in the context menu
Consolidate (or insert) the refactoring features granted by PowerShell Pro Tools into the existing refactoring feature of VS. Code.
Recall that Ctrl+Shift+R is the VS Code built-in refactoring while Ctrl+Alt+R is the PowerShell Pro Tools premium refactoring.
It might be optimal to (somehow) differentiate between built-in refactoring vs. PowerShell Pro Tools granted refactoring in the respective menu
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is your feature request related to a problem? Please describe.
Yes, it can be a little confusing that there are two refactor options available in the context menu
Describe the solution you'd like
Consolidate (or insert) the refactoring features granted by PowerShell Pro Tools into the existing refactoring feature of VS. Code.
Describe alternatives you've considered
Recall that Ctrl+Shift+R is the VS Code built-in refactoring while Ctrl+Alt+R is the PowerShell Pro Tools premium refactoring.
Additional context
It might be optimal to (somehow) differentiate between built-in refactoring vs. PowerShell Pro Tools granted refactoring in the respective menu
The text was updated successfully, but these errors were encountered: