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
no-invalid-at-rules
Generate fewer warnings
A new option
@tailwind base; @tailwind components; @tailwind utilities;
Here is a minimal reproduction of the current state of things. https://stackblitz.com/edit/no-irregular-whitespace-ey1hdv5b
Currently, the rule shows an error, as it does not understand Tailwind's custom @tailwind at rule.
@tailwind
/home/projects/better-tailwind-support/tailwind.css 1:1 error Unknown at-rule '@tailwind' found css/no-invalid-at-rules 2:1 error Unknown at-rule '@tailwind' found css/no-invalid-at-rules 3:1 error Unknown at-rule '@tailwind' found css/no-invalid-at-rules
We should introduce a new option to the rule, so we can add other supported custom at rules, like @tailwind.
I would expect the configuration to look something like this:
"css/no-invalid-at-rules": ["error", "@tailwind", "@other", ...]
/cc @JoshuaKGoldberg
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What rule do you want to change?
no-invalid-at-rules
What change do you want to make?
Generate fewer warnings
How do you think the change should be implemented?
A new option
Example code
What does the rule currently do for this code?
Here is a minimal reproduction of the current state of things.
https://stackblitz.com/edit/no-irregular-whitespace-ey1hdv5b
Currently, the rule shows an error, as it does not understand Tailwind's custom
@tailwind
at rule.What will the rule do after it's changed?
We should introduce a new option to the rule, so we can add other supported custom at rules, like
@tailwind
.I would expect the configuration to look something like this:
Participation
Additional comments
/cc @JoshuaKGoldberg
The text was updated successfully, but these errors were encountered: