We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
null
The problem
When disallowing a property with the ESLint plugin, the error message is:
{property} value must be one of: {reason}
While not completely incorrect, it's slightly misleading to say value must be one of: when there is no valid value.
value must be one of:
Without knowing how the rule is defined, it's also possible to confuse the {reason} as the possible value.
{reason}
How to reproduce
ESLint configuration
Error message
Expected behavior
I expect the error message to clearly indicate that the property is disallowed.
e.g.
Using {property} is not allowed. {reason}
Environment (include versions). Did this work in previous versions?
@stylexjs/eslint-plugin@0.4.1
It seems like a good first issue, so let me know if you'd like me to tackle it 🫡
The text was updated successfully, but these errors were encountered:
@tjosepo Yes, this is a known issue. You're welcome to take a crack at it, but I wouldn't say it's the easiest issue to tackle!
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
The problem
When disallowing a property with the ESLint plugin, the error message is:
While not completely incorrect, it's slightly misleading to say
value must be one of:
when there is no valid value.Without knowing how the rule is defined, it's also possible to confuse the
{reason}
as the possible value.How to reproduce
ESLint configuration
Error message
Expected behavior
I expect the error message to clearly indicate that the property is disallowed.
e.g.
Environment (include versions). Did this work in previous versions?
It seems like a good first issue, so let me know if you'd like me to tackle it 🫡
The text was updated successfully, but these errors were encountered: