8000 Comparing v4.0.10...v4.0.11 · tailwindlabs/tailwindcss · GitHub
[go: up one dir, main page]

Skip to content
8000
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.
base repository: tailwindlabs/tailwindcss
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v4.0.10
Choose a base ref
...
head repository: tailwindlabs/tailwindcss
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v4.0.11
Choose a head ref
  • 6 commits
  • 32 files changed
  • 3 contributors

Commits on Mar 5, 2025

  1. Ensure -- is allowed inside candidates (#16972)

    This PR fixes an issue where named utilities that contain double dashes
    `--` are not extracted correctly.
    
    Some people use `--` in the middle of the utility to create some form of
    namespaced utility.
    
    Given this input:
    ```js
    let x = 'foo--bar'
    ```
    
    The extracted candidates before this change:
    ```js
    [ "let", "x", "--bar" ]
    ```
    
    The extracted candidates after this change:
    ```js
    [ "let", "x", "foo--bar", "--bar" ]
    ```
    
    The reason `--bar` is still extracted in both cases is because of the
    CSS variable machine. We could improve its extraction by checking its
    boundary characters but that's a different issue.
    
    For now, the important thing is that `foo--bar` was extracted.
    
    # Test plan
    
    1. Added new test
    2. Existing tests pass
    RobinMalfait authored Mar 5, 2025
    Configuration menu
    Copy the full SHA
    9c59b07 View commit details
    Browse the repository at this point in the history

Commits on Mar 6, 2025

  1. Ensure classes containing number followed by dash or underscore are e…

    …xtracted correctly (#16980)
    
    Fixes #16978, and also added support for dash.
    Classes like `text-theme1-primary` or `text-theme1_primary` should be
    treated as valid.
    
    If this approach is not aligned with the project’s direction or there
    are any concerns, please feel free to close or edit this PR 😃
    
    <br/>
    
    ### As is
    
    Classes conatining number followed by dash or underscore (e.g.
    `bg-theme1-primary`, `text-title1_strong`) are ignored, and utility
    classes are not generated.
    
    ### To be
    
    Classes conatining number followed by dash or underscore (e.g.
    `bg-theme1-primary`, `text-title1_strong`) are treated as valid
    tailwindcss classes
    
    ---------
    
    Co-authored-by: Philipp Spiess <hello@philippspiess.com>
    woohm402 and philipp-spiess authored Mar 6, 2025
    Configuration menu
    Copy the full SHA
    4a02364 View commit details
    Browse the repository at this point in the history
  2. Oxide: Extract arbitrary container queries (#16984)

    Closes #16982
    
    Handle the case of variants looking like this: `@[32rem]:flex`.
    
    ## Test plan
    
    Added regression tests
    
    Co-authored-by: Robin Malfait <malfait.robin@gmail.com>
    philipp-spiess and RobinMalfait authored Mar 6, 2025
    Configuration menu
    Copy the full SHA
    617b7ab View commit details
    Browse the repository at this point in the history
  3. Fix Slim attributes (#16985)

    This PR fixes an issue in Slim templates where the start of attributes
    causes some candidates to be missing.
    
    
    ```slim
    .text-xl.text-red-600[
      data-foo="bar"
    ]
      | This line should be red
    ```
    
    Because of the `[` attached to the `text-red-600`, the `text-red-600`
    was not extracted because `[` is not a valid boundary character.
    
    To solve this, we copied the Pug pre processor and created a dedicated
    Slim pre processor. Next, we ensure that we replace `[` with ` ` in this
    scenario (by also making sure that we don't replace `[` where it's
    important).
    
    Additionally, we noticed that `.` was also replaced inside of arbitrary
    values such as URLs. This has been fixed for both Pug and Slim.
    
    Fixes: #16975
    
    # Test plan
    
    1. Added failing tests
    2. Existing tests still pass
    RobinMalfait authored Mar 6, 2025
    Configuration menu
    Copy the full SHA
    af132fb View commit details
    Browse the repository at this point in the history
  4. Ensure arbitrary variables with data types are extracted correctly (#…

    …16986)
    
    Closes #16983
    
    This PR fixes an issue where the arbitrary variable machine did not
    extract data type correctly.
    
    ## Test plan
    
    - Added regression test
    philipp-spiess authored Mar 6, 2025
    Configuration menu
    Copy the full SHA
    bff387b View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    b676da8 View commit details
    Browse the repository at this point in the history
Loading
0