-
-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
fix(runtime-core): type ExposedKeys removed defined properties on com… #12697
base: main
Are you sure you want to change the base?
Conversation
This change will break the existing test case in By the way, could you provide a test case or a minimal reproduction to clarify the issue this PR is addressing? Thanks! |
Size ReportBundles
Usages
|
@vue/compiler-core
@vue/compiler-dom
@vue/compiler-ssr
@vue/reactivity
@vue/compiler-sfc
@vue/runtime-core
@vue/runtime-dom
@vue/server-renderer
@vue/shared
vue
@vue/compat
commit: |
I can confirm this issue using Webstorm LTS 2024.2.5 Build #WS-242.24807.6 It is however, only the case if I'm using class based components using vue-facing-decorator. Using the composition API, the component resolves correctly. We have a lot of older projects at our company for which there is no budget to convert them to composition API, so for us it is a pretty common and annoying problem. |
It took whole weekend to figure out where this issue with Intellij ideas came from. I will look at the tests when I have time again. Probably end of the week. |
Do you have any updates on this by any chance? |
Fixed the test. |
Fixes typo made in pull request #3399.
IDEs using Vue language service with TypeScript support will have all the local component variables displayed as red with an error
Vue: X does not exist on type
.ExposedKeys
will compare empty string ('') to extendExposed
type which will always fail cause builtin string can't extend custom class.Tested with:
PHPStrom 2024.3.1.1
TypeScript 5.7.3
Vue LS 2.2.0