-
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
Site editor: prune store constants #54585
Conversation
Size Change: -46 B (0%) Total Size: 1.62 MB
ℹ️ View Unchanged
|
Flaky tests detected in fcd885e. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/6231917030
|
973419c
to
bf5e6d3
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.
Looking good!
✅ All replaced hard-coded strings look correct
✅ Removed constants weren't being used anywhere
✅ Template part modal and patterns categories behaviour works as on trunk
LGTM! ✨
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 👍
I just cherry-picked this PR to the release/16.7 branch to get it included in the next release: 0d18f06 |
* Consolidate and prune edit site store constants for template part strings * Rename TEMPLATE_PART_AREA_GENERAL to TEMPLATE_PART_AREA_DEFAULT_CATEGORY
What?
Consolidate and prune edit site store constants for template part strings
Why?
When working on #54484 I noticed that some constants in the edit site store weren't being used.
One was, and I moved it over to a centralized file.
Testing Instructions
Tests should pass. Imports shouldn't break build :)
Create template part modal should work as expected