-
-
Notifications
You must be signed in to change notification settings - Fork 594
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
Support analyzing vue-class-component #1105
Comments
It is also important to note that vue-class-component is often used along with the vue-property-decorator for defining props |
Is this going to be a tough one or are we likely to see it in a near-future release? |
I'd like to limit this issue to only vue-class-component, which is officially supported. There are many decorator libraries such as https://github.com/kaorun343/vue-property-decorator, https://github.com/itsFrank/vue-typescript, and one in the upcoming Vue 3 vuejs/rfcs#17. Supporting them all is likely a lot of maintenance. |
I think that's a reasonable compromise. |
@octref @dennis2k Here the bug: |
Hi anyone, I publish self-maintenance vscode extension. https://marketplace.visualstudio.com/items?itemName=yoyo930021.vuter |
Continuing #1083
ComponentInfo
is not able to analyzevue-class-component
yet.The source looks like below, so it needs a different AST visitor. Maybe we can use typing from
vue-class-component
to analyze it.The text was updated successfully, but these errors were encountered: