No description
This PR fixes a bug where CSS was generated for `start` and `end`. This was accidentally introduced when we moved the `start-*` and `end-*` utilities to the legacy utilities. But this meant that we now generate CSS for `start` and `end` even if no value is provided. Fixes: #20002 ## Test plan 1. Updated the tests to make sure of `--spacing: 0.25rem` which made the tests fail, and are fixed again by applying the fix. 2. Other tests are still passing |
||
|---|---|---|
| .github | ||
| crates | ||
| integrations | ||
| packages | ||
| patches | ||
| playgrounds | ||
| scripts | ||
| .gitignore | ||
| .prettierignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CHANGELOG.md | ||
| LICENSE | ||
| package.json | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| README.md | ||
| rust-toolchain.toml | ||
| turbo.json | ||
| vitest.config.ts | ||
A utility-first CSS framework for rapidly building custom user interfaces.
Documentation
For full documentation, visit tailwindcss.com.
Community
For help, discussion about best practices, or feature ideas:
Discuss Tailwind CSS on GitHub
Contributing
If you're interested in contributing to Tailwind CSS, please read our contributing docs before submitting a pull request.