-
-
Notifications
You must be signed in to change notification settings - Fork 681
Proposition ~ environments: vuex
, vue-router
#102
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
Comments
vuex
, vue-router
vuex
, vue-router
I think this is a really interesting idea and we should definitely investigate it, though @mysticatea might already have better insights based on his work in eslint organization. Plugins like |
I'm sorry for late. For example: {
"extends": ["eslint:recommended", "plugin:vue/recommended"],
"settings": {
"vue": {
"env": {
"vuex": true,
"vue-route": true
}
}
}
} |
Cool @mysticatea , then I think we can close this issue @armano2. Seems like we have an option and it just needs to be implemented on a specific rule if needed, there is no other work to be done in order to configure it apart from adding default values in base config and documenting it. |
I was thinking a little how to allow/disallow functions from official plugins
vuex
andvue-route
, and i don't want to add by default rules to tell that names are reserved, or you can use this component etc....I think we need some sort of flags to disable/enable official plugin support. If its possible in similar way as
Environments
are set up in eslint.By default support both of plugins should be enabled but optionally user will be able to disable them.
Let me know what do you think about this
The text was updated successfully, but these errors were encountered: