Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stop emitting mixed-decls in a bunch of unnecessary cases #2342

Merged
merged 2 commits into from
Sep 13, 2024

Conversation

nex3
Copy link
Contributor

@nex3 nex3 commented Sep 13, 2024

@nex3 nex3 merged commit f826ed2 into main Sep 13, 2024
38 checks passed
@nex3 nex3 deleted the mixed-decls-improvement branch September 13, 2024 22:36
: valueSpanForMap = valueSpanForMap ?? value.span {
{required this.parsedAsCustomProperty,
Iterable<CssStyleRule>? interleavedRules,
this.trace,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The docs say this isn't set when interleavedRules is empty, but I could make an object that's the opposite of that. Should this have a validation that ensures trace will be null when interleavedRules is null or empty? Or should the documentation on the AST node say that the behavior of trace is undefined when interleavedRules is empty?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants