-
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
Font Library: address feedback from wordpress-develop#6027 #58691
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 Core SVNIf you're a Core Committer, use this list when committing to
GitHub Merge commitsIf 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. |
This pull request has changed or added PHP files. Please confirm whether these changes need to be synced to WordPress Core, and therefore featured in the next release of WordPress. If so, it is recommended to create a new Trac ticket and submit a pull request to the WordPress Core Github repository soon after this pull request is merged. If you're unsure, you can always ask for help in the #core-editor channel in WordPress Slack. Thank you! ❤️ View changed files❔ lib/compat/wordpress-6.5/fonts/class-wp-font-collection.php ❔ lib/compat/wordpress-6.5/fonts/class-wp-font-library.php ❔ lib/compat/wordpress-6.5/fonts/fonts.php |
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.
This PR captures all of the feedback in Core's PR.
The only exception: whether to assign a WP_Error
for the font collection slug mismatch in its constructor. But this is a discussion and not yet ready to be actioned. Thinking the discussion could be a follow-up in Core once there's consensus and if changes are needed.
The PR LGTM 👍
Flaky tests detected in 4d8472a. 🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/7790546483
|
What?
Addresses initial feedback from WordPress/wordpress-develop#6027
Why?
We're updating the code in Gutenberg first, and then updating the wordpress-develop PR to keep the Gutenberg and proposed Core code in sync.
Testing Instructions
No functional changes. Check that phpunit tests pass and feature continues to work as expected.