-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Global Styles: rename core
origin key to default
for presets
#36645
Global Styles: rename core
origin key to default
for presets
#36645
Conversation
Size Change: -1 B (0%) Total Size: 1.1 MB
ℹ️ View Unchanged
|
core
origin key to default
for presets
@@ -215,7 +215,7 @@ const PanelColorGradientSettingsMultipleSelect = ( props ) => { | |||
|
|||
const customGradients = useSetting( 'color.gradients.user' ); | |||
const themeGradients = useSetting( 'color.gradients.theme' ); | |||
const defaultGradients = useSetting( 'color.gradients.core' ); | |||
const defaultGradients = useSetting( 'color.gradients.default' ); |
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.
I guess this one might be a breaking change? Should we provide an alias or maybe it's fine for this one?
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.
I think it is fine origins were never exposed in the core.
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.
I think I still see a couple places to change:
- packages/edit-site/src/components/global-styles/use-global-styles-output.js
- phpunit/class-wp-theme-json-test.php
3f76cd9
to
fb4821e
Compare
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.
LGTM 👍
Hey there 👋 I was wondering if there's a way for future changes like these to still support a previous naming? The mobile editor uses a global style endpoint where it gets the colors configuration including |
Renames core origin key to default.
I verified global styles continue to work as before.