Skip to content
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: 3f0388959626a01c5778fdf92de697d01a7cf557
Choose a base ref
...
head repository: tailwindlabs/tailwindcss
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 093db284e8ffb3d506edc0e283345bcf938ed0ed
Choose a head ref
  • 7 commits
  • 12 files changed
  • 1 contributor

Commits on Sep 30, 2021

  1. Detect ambiguity in arbitrary values (#5634)

    * detect ambiguity in arbitrary values
    
    * update warning message
    RobinMalfait authored Sep 30, 2021
    Configuration menu
    Copy the full SHA
    11bfa0a View commit details
    Browse the repository at this point in the history
  2. immediately take the safelist values into account

    Currently we had to manually add them in the `setupTrackingContext`,
    `setupWatchingContext` and the `cli`.
    
    This was a bit cumbersome, because the `safelist` function (to resolve
    regex patterns) was implemented on the context. This means that we had
    to do something like this:
    
    ```js
    let changedContent = []
    let context = createContext(config, changedContent)
    for (let content of context.safelist()) {
      changedContent.push(content)
    }
    ```
    
    This just feels wrong in general, so now it is handled internally for
    you which means that we can't mess it up anymore in those 3 spots.
    RobinMalfait committed Sep 30, 2021
    Configuration menu
    Copy the full SHA
    2340987 View commit details
    Browse the repository at this point in the history
  3. drop the dot from the extension

    Our transformers and extractors are implemented for `html` for example.
    However the `path.extname()` returns `.html`.
    
    This isn't an issue by default, but it could be for with custom
    extractors / transformers.
    RobinMalfait committed Sep 30, 2021
    Configuration menu
    Copy the full SHA
    28deda0 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    a5e5268 View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    9af1eaa View commit details
    Browse the repository at this point in the history
  6. ensure we always have an extension

    Defaults to `html`
    RobinMalfait committed Sep 30, 2021
    Configuration menu
    Copy the full SHA
    c464c3f View commit details
    Browse the repository at this point in the history
  7. Configuration menu
    Copy the full SHA
    093db28 View commit details
    Browse the repository at this point in the history
Loading