Skip to content
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

Tailwind CSS multiple file extension content pattern #988

Merged
merged 1 commit into from Apr 28, 2023

Conversation

cossssmin
Copy link
Member

@cossssmin cossssmin commented Apr 28, 2023

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:

module.exports = {
  build: {
    templates: {
      filetypes: ['html', 'yaml'],
      source: 'src/templates',
    }
  }
}

The automatically-generated content path was:

'src/templates/**/*.html,yaml'

While Tailwind doesn't warn about it, the pattern won't work to search in all html and yaml files at that location, resulting in some CSS not being generated. With this fix, it will be correctly generated to:

'src/templates/**/*.{html,yaml}'

@cossssmin cossssmin merged commit d45f1e2 into master Apr 28, 2023
3 checks passed
@cossssmin cossssmin deleted the fix/tailwindcss-content-patterns branch December 29, 2023 14:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant