[Oxide] Ensure generated tailwind.config.js file is formatted properly
#11221
Conversation
This file contains 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
The `\s` regex includes newlines `\n`, but we only want leading spaces to be removed.
RobinMalfait
changed the title
tailwind.config.js is formatted properlytailwind.config.js file is formatted properly
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 PR fixes a small formatting issue when generating the
tailwind.config.jsfile when using thenpx tailwindcss initcommand using the oxide engine.We dropped the
content: []by default such that the auto content detection can be used as a default. However we used a regex to replace thecontent: []which included a\sin the regex.This is problematic because
\sincludes\nso therefore the previous\nwas removed as well.Everything still worked, but the formatting of the generated file was off.