-
Notifications
You must be signed in to change notification settings - Fork 120
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
feat: integrate code refactorings from language-service via LSP #2050
Conversation
Blocked on angular/angular#56895 |
This is a performance optimization that would exit early when code actions are requested, but we know Angular cannot provide fixes based on the error codes. Previously, we would unnecessarily compute and analyze the application for semantic diagnostics. This will be helpful for: angular/vscode-ng-language-service#2050
This is a performance optimization that would exit early when code actions are requested, but we know Angular cannot provide fixes based on the error codes. Previously, we would unnecessarily compute and analyze the application for semantic diagnostics. This will be helpful for: angular/vscode-ng-language-service#2050 PR Close #57000
@atscott Take a look at this PR. A public API called getSupportedCodeFixes is used to check if the compiler can fix the diagnostics. Remove the unnecessary export custom API. |
d3e4d05
to
1479833
Compare
Note: This PR also bumps to a next release of the language service. Not sure if this is fine for the versioning in this repository— but I assume yes, given that there is a 18.x branch |
This integrates Angular's code refactorings into the extension, so that those are communicated via the LSP to VSCode.
1479833
to
04eb510
Compare
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
This integrates Angular's code refactorings into the extension, so that those are communicated via the LSP to VSCode.