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.
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
Edit block style variations from global styles #46343
Edit block style variations from global styles #46343
Changes from all commits
85a9598
6c065bf
6943f00
9f89d2e
d6bf36b
fd3451b
91350f4
564fd4e
822b800
201f6a0
6e9f10c
df3c408
79d760b
6cfb120
3467f9d
fa02475
60d95e2
174f1c7
510aa3f
25048fe
8dab200
aac1e1b
d8972ce
967e319
127305a
513db1c
a6b2d9c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a blocker, but I wonder if in a follow-up there's an opportunity to either consolidate some of this logic with the feature declarations above, or split it out into a separate function, since this function is now quite long? Definitely not something to worry about in this PR, just jotting down the thought 🙂
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It took me a second to work out why this area has two calls to
compute_style_properties
. It looks like the second call here is for anything not already covered by feature level selectors (since the feature level ones will have unset the feature from the$style_variation_node
).Would it be worth adding a comment prior to this line, something along the lines of "Compute declarations for remaining styles not covered by feature level selectors" or something like that?