-
-
Notifications
You must be signed in to change notification settings - Fork 664
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 detect Nuxt3 defineNuxtComponent #2311
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your contribution!
@FloEdelmann |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🙂
@ota-meshi Should we consider this a breaking change and keep this for v10? (see #2166)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Sorry for the late review.
Yeah. I think this should be included in v10. |
vue/no-unused-properties
does not work withdefineNuxtComponent()
#2191vue/order-in-components
is not working withdefineNuxtComponent()
#2057Description
It's just a workaround like solution.
Add the
defineNuxtComponent
alias for Nuxt3 projects, similar to #1088.About defineNuxtComponent
The difference between
defineNuxtComponent
anddefineComponent
is onlyasyncData
andhead
options are added ondefineNuxtComponent
.These options are not essential to check in vue-eslint-plugin, so it should be fine to treat it as
defineComponent
.https://nuxt.com/docs/api/utils/define-nuxt-component