Add support for @source inline and not inline syntax #19
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for Tailwind 4's
@source inlineand@source not inlinesyntax, which was previously causing validation errors in ESLint CSS rules.Problem
The
@sourceat-rule was defined with a too-restrictive prelude pattern of<string>, which only allowed simple string literals. This caused validation failures for the new Tailwind 4 syntax:These would produce errors like:
Solution
Updated the
@sourceprelude definition intailwind4.jsto support the official Tailwind CSS 4 syntax patterns:@source inline("class1", "class2")- for safelisting specific utilities@source not inline("class")- for explicitly excluding classesThe new prelude pattern is:
inline( <string># ) | not inline( <string># )Changes
@sourceprelude definition insrc/tailwind4.jsVerification
The implementation correctly handles:
@source inline("{hover:,focus:,}underline")@source inline("class1", "class2", "class3")@source not inline('container')Edge cases are properly validated:
@source inline())Fixes #18.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.