Implement support for parsing custom at rules in JS bindings #395
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.
Closes #391
This adds a new configuration option to the Lightning CSS JavaScript API which enables basic parsing of custom at-rules into a more structured AST rather than storing raw tokens. You can configure how the prelude and block should be parsed, and then use the value to transform the rule if needed. The syntax for the prelude is defined using a syntax string (as used in the
@property
rule), and the block can be a "declaration-list", "rule-list", or "style-block" as defined in the css spec.In this example,
@breakpoints
accepts a rule list as a body, and@test
accepts a style block, i.e. either a declaration list (in nested style rules) or a rule list.@test
also expects a comma separated list of identifiers as a prelude.To do