Skip to content

Ambiguous documentation about eslint/vue3-recommended and eslint/vue-recommended plugins #2708

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

Closed
2 tasks done
scoutme opened this issue Mar 6, 2025 · 1 comment · Fixed by #2709
Closed
2 tasks done

Comments

@scoutme
Copy link

scoutme commented Mar 6, 2025

Checklist

  • I have tried restarting my IDE and the issue persists.
  • I have read the FAQ and my problem is not listed.

Tell us about your environment

  • ESLint version: 8.57.0
  • eslint-plugin-vue version: 9.17.0
  • Vue version: 3
  • Node version: 20.9.0
  • Operating System: Ubuntu (both WSL2 and native)

Please show your full configuration:

n/a

What did you do?

n/a

What did you expect to happen?
Reading documentation about vue3 eslint configuration I expect coherent information about plugins and rules

What actually happened?
In documentation I read:

Priority A: Essential (Error Prevention)
3️⃣ Indicates that the rule is for Vue 3 and is included in all of "plugin:vue/essential", .configs["flat/essential"], >"plugin:vue/strongly-recommended", .configs["flat/strongly-recommended"], "plugin:vue/recommended" and >.configs["flat/recommended"] presets.
2️⃣ Indicates that the rule is for Vue 2 and is included in all of "plugin:vue/vue2-essential",
.configs["flat/vue2->essential"], "plugin:vue/vue2-strongly-recommended",.configs["flat/vue2-strongly-recommended"] and >"plugin:vue/vue2-recommended",.configs["flat/vue2-recommended"] presets.

(vu3-recommended is referenced in the first source, and disappears in second)

Repository to reproduce this issue

@FloEdelmann
Copy link
Member

Thanks for letting us know, we did in fact forget to update these in #2648. I fixed it in #2709.

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

Successfully merging a pull request may close this issue.

2 participants