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 v-bind same name shorthand #2355

Closed
Tracked by #2326
beefchimi opened this issue Jan 4, 2024 · 2 comments · Fixed by #2357
Closed
Tracked by #2326

Support v-bind same name shorthand #2355

beefchimi opened this issue Jan 4, 2024 · 2 comments · Fixed by #2357

Comments

@beefchimi
Copy link

What rule do you want to change?

Does this change cause the rule to produce more or fewer warnings?

How will the change be implemented? (New option, new default behavior, etc.)?

  • I think we simply need to update the rule to allow shorthand props.

Please provide some example code that this change will affect:

<SomeComponent :disabled :custom />

What does the rule currently do for this code?

  • Currently, using shorthand will produce the following error:

screen

What will the rule do after it's changed?

  • No longer complain when a valid shorthand syntax is used.

Additional context

  • Attempted using the shorthand syntax in a project with the following dependencies:
"dependencies": {
  "vue": "^3.4.5"
},
"devDependencies": {
  "@rushstack/eslint-patch": "^1.6.1",
  "@tsconfig/node20": "^20.1.2",
  "@types/node": "^20.10.6",
  "@vitejs/plugin-vue": "^5.0.2",
  "@vue/eslint-config-prettier": "^9.0.0",
  "@vue/eslint-config-typescript": "^12.0.0",
  "@vue/tsconfig": "^0.5.1",
  "eslint": "^8.56.0",
  "eslint-plugin-vue": "^9.19.2",
  "lightningcss": "^1.22.1",
  "npm-run-all2": "^6.1.1",
  "prettier": "^3.1.1",
  "typescript": "^5.3.3",
  "vite": "^5.0.10",
  "vite-plugin-svg-sprite": "^0.5.1",
  "vue-tsc": "^1.8.27"
}
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.

4 participants