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
Chore: add internal rule that validates meta property (fixes #6383) #6608
Conversation
LGTM |
@@ -12,3 +12,5 @@ versions.json | |||
.eslintcache | |||
.cache | |||
/packages/**/node_modules | |||
.vscode/setting.json | |||
.sublimelinterrc |
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.
Are there any other editor lint settings that we should add?
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.
We just add them as we go, so I wouldn't worry about it right now.
I'm okay with the folder name, but what do you think about prefixing the rule with "eslint-" instead of "internal-"? |
@platinumazure I think |
/** | ||
* Gets the property of the Object node passed in that has the name specified. | ||
* | ||
* @param {String} property Name of the property to return. |
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.
{string}
(lowercase)
@vitorbal this looks great! Just a few small things to address. |
Thanks everyone for the great feedback! I will get to this later this weekend or sometime next week! |
LGTM |
LGTM |
Lgtm. Awesome work. |
Thanks everyone! 😄 |
Add a custom rule to verify that all core rules have the correct
meta
property format.As discussed in #6383 this is just an internal custom rule for now and not a plugin.
I modified the Makefile's lint task so it find our "internal rules" directory. Feedback welcome on a better folder name.