-
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
Block Editor: Unlock private setting keys at the file level #61813
Conversation
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.
To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
There's a few left: gutenberg/packages/block-editor/src/components/colors-gradients/control.js Lines 109 to 112 in 0f68078
gutenberg/packages/block-editor/src/components/global-styles/color-panel.js Lines 210 to 213 in 0f68078
|
Size Change: -17 B (0%) Total Size: 1.75 MB
ℹ️ View Unchanged
|
Yes, the circular dependency issue was resolved in #61102. |
Flaky tests detected in ade98bd. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/9171026024
|
…s#61813) * Block Editor: Unlock private setting keys at the file level * Feedback Co-authored-by: Mamaduka <mamaduka@git.wordpress.org> Co-authored-by: ellatrix <ellatrix@git.wordpress.org>
…s#61813) * Block Editor: Unlock private setting keys at the file level * Feedback Co-authored-by: Mamaduka <mamaduka@git.wordpress.org> Co-authored-by: ellatrix <ellatrix@git.wordpress.org>
What?
A micro-optimization unlocks private setting keys (
Symbol
) at the file level. These values don't change with the component life-cycle.Testing Instructions
CI checks are green.