mirror of
https://github.com/tailwindlabs/tailwindcss.git
synced 2025-12-08 21:36:08 +00:00
49484f0491
This PR fixes an issue where we migrated classes such as `rounded` to `rounded-sm` (see: https://github.com/tailwindlabs/tailwindcss/pull/14875) However, if you override the values in your `tailwind.config.js` file, then the migration might not be correct. This PR makes sure to only migrate the classes if you haven't overridden the values in your `tailwind.config.js` file. --------- Co-authored-by: Philipp Spiess <hello@philippspiess.com>
50 lines
1.7 KiB
TypeScript
50 lines
1.7 KiB
TypeScript
import type { Config } from 'tailwindcss'
|
|
import { parseCandidate } from '../../../../tailwindcss/src/candidate'
|
|
import type { DesignSystem } from '../../../../tailwindcss/src/design-system'
|
|
import { printCandidate } from '../candidates'
|
|
import { isSafeMigration } from '../is-safe-migration'
|
|
|
|
// In v3 the important modifier `!` sits in front of the utility itself, not
|
|
// before any of the variants. In v4, we want it to be at the end of the utility
|
|
// so that it's always in the same location regardless of whether you used
|
|
// variants or not.
|
|
//
|
|
// So this:
|
|
//
|
|
// !flex md:!block
|
|
//
|
|
// Should turn into:
|
|
//
|
|
// flex! md:block!
|
|
export function important(
|
|
designSystem: DesignSystem,
|
|
_userConfig: Config,
|
|
rawCandidate: string,
|
|
location?: {
|
|
contents: string
|
|
start: number
|
|
end: number
|
|
},
|
|
): string {
|
|
nextCandidate: for (let candidate of parseCandidate(rawCandidate, designSystem)) {
|
|
if (candidate.important && candidate.raw[candidate.raw.length - 1] !== '!') {
|
|
// The important migration is one of the most broad migrations with a high
|
|
// potential of matching false positives since `!` is a valid character in
|
|
// most programming languages. Since v4 is technically backward compatible
|
|
// with v3 in that it can read `!` in the front of the utility too, we err
|
|
// on the side of caution and only migrate candidates that we are certain
|
|
// are inside of a string.
|
|
if (location && !isSafeMigration(location)) {
|
|
continue nextCandidate
|
|
}
|
|
|
|
// The printCandidate function will already put the exclamation mark in
|
|
// the right place, so we just need to mark this candidate as requiring a
|
|
// migration.
|
|
return printCandidate(designSystem, candidate)
|
|
}
|
|
}
|
|
|
|
return rawCandidate
|
|
}
|