refactor: allow overriding email comb selector safelist #975
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 changes the way
removeUnusedCSS
behaves, allowing you to completely override its selectors safelist from yourconfig.js
. This was necessary so that email client targeting selectors do not show up in all of your project's templates when you just want to use a one-off. They would normally show up because Tailwind CSS is compiled once for all templates, and then is purged on a template-basis.Maizzle won't remove these selectors in the first pass, but with this change you can now run a quick second pass to remove unnecessary client targeting selectors from templates that don't need them: