Use palette generator conditionally #2003
Open
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.
Description
This PR updates the PostCSS configuration such that the plugin generating the color palette JSON file from the CSS file is only used when the current file's name contains the word "theme".
Motivation and Context
While it is sufficient to generate the plugin for the theme.css file only, for each
npm run css
the JSON file is generated for theme.css and for custom-editor-style.css.If one wants to use the same PostCSS config for any other file - say a custom.css - the plugin is used as well. This probably creates edge cases where the actual color palette JSON is overwritten by the palette created from custom.css.
Types of changes
Checklist:
develop
.develop
.composer cs:check
has passed locally.composer lint:php
has passed locally.