-
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 Outstanding Feedback from WP 6.4 review #58675
Conversation
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/class-wp-font-utils.php ❔ lib/compat/wordpress-6.5/fonts/class-wp-rest-font-collections-controller.php ❔ lib/compat/wordpress-6.5/fonts/class-wp-rest-font-faces-controller.php ❔ lib/compat/wordpress-6.5/fonts/class-wp-rest-font-families-controller.php ❔ phpunit/tests/fonts/font-library/wpRestFontFacesController.php |
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. |
@@ -194,7 +194,7 @@ private function sanitize_and_validate_data( $data ) { | |||
if ( empty( $data[ $property ] ) ) { | |||
$message = sprintf( | |||
// translators: 1: Font collection slug, 2: Missing property name. | |||
__( 'Font collection "%1$s" has missing or empty property: "%2$s."', 'gutenberg' ), | |||
__( 'Font collection "%1$s" has missing or empty property: "%2$s".', 'gutenberg' ), |
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.
@@ -162,7 +162,7 @@ private function load_from_url( $url ) { | |||
|
|||
$data = json_decode( wp_remote_retrieve_body( $response ), true ); | |||
if ( empty( $data ) ) { | |||
return new WP_Error( 'font_collection_decode_error', __( 'Error decoding the font collection data from the REST response JSON.', 'gutenberg' ) ); | |||
return new WP_Error( 'font_collection_decode_error', __( 'Error decoding the font collection data from the http response JSON.', 'gutenberg' ) ); |
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'd assume HTTP to be capitalized here.
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.
Updated here: 59e6fde
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 went through the comments on the previous Font Library Core PR, and tried to uncover all of the hidden and previously resolved comments.
To my knowledge, these changes address the outstanding feedback there.
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.
The changes made LGTM.
Note: I did not cross-reference with the original PR to ensure all feedback is addressed. That said, I'm sure @getdave @creativecoder @matiasbenedetto did a great job.
What?
This PR applies any feedback that may have been missed from a review on the original Fonts proposal for WP 6.4 which happened on WordPress/wordpress-develop#5285.
Why?
Much of the review is now outdated and is largely stale. Nonetheless, this is a good opportunity to pick up on any queries that have previously been raised as it is easy to miss things from months ago.
How?
Applies any outstanding feedback where it could be identified and applied directly without further discussion.
Any further feedback should now happen on the new Core PR(s) for the Font Library.
Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast