feat: find correct child components' definition inside template region #2075
Conversation
This file contains hidden or 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
|
Sorry for the LSP tests paths, long time after my first commit. I've merged the master branch and fixed some conflicts. |
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.
NOTE: This is a copy of PR 1760, sorry that I republish original branch fixing conflicts but got messed up by github's workflow, had to create a new PR here.
This PR will add support for #1712.
I notice that there is already vueFileInfo.componentInfo.childComponents provided by the implementation of Vue interpolation. But during definition-finding for html, a little case issue causes this functionality to fail, typically when component filenames adopt a PascalCase convention.