fix: misc aura/lwc lsp bug fixes, support lwc component methods in tree, unknown project types #1232
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
April 3, 2019 13:17
midzelis
changed the title
added 2 commits
April 8, 2019 10:58
This was referenced Jan 22, 2022
This was referenced Oct 6, 2022
This was referenced Nov 5, 2022
This was referenced Dec 26, 2022
This was referenced Jun 20, 2023
This was referenced Nov 28, 2023
This was referenced May 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Bug fixes, and support for unknown project types
What issues does this PR fix or reference?
fix: build: Remove hard dependency on vscode-core
fix: component-tree: show method icon for lwc component methods
fix: component-tree: display no components message when no components found
fix: component-tree: filter aura/lwc system namespaces for unknown workspaces, when no custom components detected
fix: telemetry: be sure to always activate vscode-core if installed
fix: lsp: launch lsp client with system version of node instead of built-in
fix: plugin: activate plugin on explorer view