-
-
Notifications
You must be signed in to change notification settings - Fork 595
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
feat: remove vuetify-helper-json and use runtime pkg info #1365
Conversation
58dba21
to
05b0fe7
Compare
05b0fe7
to
4056e3d
Compare
settings['vuetify'] = true; | ||
} | ||
if (dependencies['@nuxtjs/vuetify'] || devDependencies['@nuxtjs/vuetify']) { | ||
dependencies['vuetify'] = true; |
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.
Shouldn't it be :
dependencies['vuetify'] = true; | |
settings['vuetify'] = true; |
?
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.
No. I am not actually 100% sure what setting the settings
object accomplishes 😕 . And since settings[dep] = true
is executed later anyway, it shouldn't matter.
The actual loading of the autocomplete data specified in vetur
package.json option happens here
for (const dep in dependencies) { |
dependencies
object. Since vuetify is not a direct dependency when using nuxtjs module, we fake it by inserting vuetify.
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.
Good catch, then all good I believe
LGTM, thanks! |
Thanks again! 💚 |
switched to using
vetur
option inside package.json for auto-completion instead of separate package.also added support through @nuxtjs/vuetify package