-
-
Notifications
You must be signed in to change notification settings - Fork 681
[New] Add prop-name-casing
#289
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
Conversation
Thanks for your work @bfkbx960 ! We really appreciate it :) We're going to merge new rules once stable v4 is out 🚀 |
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 job @bfkbx960 👍 I left two comments though, update PR and we're ready to 🚢 it :)
lib/rules/prop-name-casing.js
Outdated
if (convertedName !== propName) { | ||
context.report({ | ||
node: item, | ||
message: 'Prop "{{name}}" is not {{caseType}}.', |
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.
I think it should be: is not in
lib/rules/prop-name-casing.js
Outdated
meta: { | ||
docs: { | ||
description: 'enforce specific casing for the Prop name in Vue components', | ||
category: 'strongly-recommended' |
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.
Can you please change the category to be upcoming
?
category: 'upcoming' // 'strongly-recommended'
We're not going to enable this rule by default until the next major release, so we'll stash them in special category for everyone to see what's going to be enabled in next version :)
@michalsnik suggestions applied, thank you for code review. |
This PR implements rule proposed in #252