Tailwind CSS multiple file extension content pattern #988
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 fixes an issue with
content
patterns for Tailwind CSS when specifying multiple file extensions for Maizzle templates.Basically if you had something like this:
The automatically-generated
content
path was:While Tailwind doesn't warn about it, the pattern won't work to search in all
html
andyaml
files at that location, resulting in some CSS not being generated. With this fix, it will be correctly generated to: