Clarify how the configFile option works with v4 #1167
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
cc @reinink would you mind taking a peek at the readme changes? |
philipp-spiess
approved these changes
Feb 5, 2025
There was a problem hiding this comment.
Bug fix LGTM, I think the changelog change is fine too but would still appreciate @reinink giving it a 👀
reinink
reviewed
Feb 5, 2025
reinink
requested changes
Feb 5, 2025
reinink
approved these changes
Feb 5, 2025
Co-authored-by: Jonathan Reinink <[email protected]>
thecrypticace
force-pushed
the
feat/clarify-config-file-option
branch
from
f4a5599 to
f4225ce
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This updates the readme to detail how the
tailwindCSS.experimental.configFileoption is meant to be used with v4.This PR also does two additional things: