-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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: Allow custom properties to merge #31840
Conversation
Size Change: 0 B Total Size: 1.32 MB ℹ️ View Unchanged
|
[edit]. I had some thoughts and went back-and-forth with myself but no longer agree with myself. Myself and I are no longer speaking about this matter so I look forward to other people's thoughts and reasonings instead. |
Is there an alternative that doesn't involve adapting the The way we deal with this in the site editor is by doing the merge in the UI: when a user adds a new color, we merge it with the colors of the theme and store them all in the user CPT. Same when the user changes the value of a color provided by a theme. Can you perhaps do the same? |
Yes we definitely can, but I'm curious as to why it was decided not to merge |
Actually. So far, You may need to rebase this from |
ce902ca
to
1d079cc
Compare
6436d5a
to
1d079cc
Compare
This is more a question/discussion than a proposal.
I am modifying the user data for theme.json (the CPT) from outside of the Site Editor (using the Customizer), by adding properties to
settings.custom
. When I do this I wantsettings.custom
from the theme.json itself to be merged with the settings from the CPT. This line wipes out the contents of settings.custom from theme.json and replaces it with the data in the CPT. I assume it's here for a good reason though.