Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 10 commits
- 21 files changed
- 5 contributors
Commits on Dec 15, 2021
-
-
-
Ensure all plugins are executed for a given candidate (#6540)
* remove early return so that all plugins are handled We had an early return so that once a plugin was matched, that we could stop running the code through the other plugins. However, in this case we have an issue that user defined css is technically also a plugin. This means that: - `bg-green-light` Would check for: - `bg-green-light` (no hit, continue) - `bg-green` (Hit! Don't execute next plugins) - `bg` (This is the one that would have generated `bg-green-light`) We tested this change and it doesn't seem to have an impact functionally and also not really performance wise. * update changelog
-
-
Add 'text-decoration-color' to default 'transition' and 'transition-c…
…olors' utilities (#6405) * Add 'text-decoration-color' to default 'transition' and 'transition-colors' utilities * Add 'text-decoration-color' to default 'transition' and 'transition-colors' utilities * Delete tailwind-output-flagged.css * Delete tailwind-output-important.css * Delete tailwind-output-no-color-opacity.css * Delete tailwind-output.css Co-authored-by: Jonathan Reinink <[email protected]>
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v3.0.5...v3.0.6