Skip to content
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 for defineOptions #2118

Closed
ota-meshi opened this issue Mar 30, 2023 · 2 comments · Fixed by #2165
Closed

Support for defineOptions #2118

ota-meshi opened this issue Mar 30, 2023 · 2 comments · Fixed by #2165

Comments

@ota-meshi
Copy link
Member

Tell us about your environment

  • ESLint version: v8.36.0
  • eslint-plugin-vue version: v9.10.0
  • Node version: v18.12.1

The problem you want to solve.

Support for defineOptions macro.

See https://github.com/vuejs/core/blob/main/CHANGELOG.md#330-alpha6-2023-03-30

Your take on the correct solution to problem.

Parser and some rules are affected. However, we have not yet listed the affected rules.
I think that, first, we need to list the rules affected by defineOptions.

Additional context

Related to vuejs/vue-eslint-parser#183

@jods4
Copy link

jods4 commented Apr 21, 2023

One affected rule is vue/multi-word-component-names.
With defineOptions({ name: 'UiForm' }) in a component form.vue, this rule should not trigger.

@ota-meshi
Copy link
Member Author

ota-meshi commented May 13, 2023

I believe I've opened PRs to change the rules affected by the addition of defineOptions.
If you think there are other rules that have an affected, please comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants