fix(compiler-sfc): support nested namespaces in global types #8102
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
innocenzi
changed the title
IAmSSH
pushed a commit
to IAmSSH/core
that referenced
this pull request
May 14, 2023
…ferring type close vuejs#8102
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.
This draft PR is an attempt at supporting references in the global types support recently added by Evan in 4e028b9.
For now the PR only contains a failing test that demonstrates the issue. cc @yyx990803 if you know how to support this — I'm still currently figuring out the source code to try and fix this myself in the meantime.
Related: #8083
EDIT: after a bit more of debugging, it seems the issue is nested namespaces actually. eg.
App.AircraftDatais recognized but notApp.Data.AircraftData.