Font Library: Remove WP_Font_Family class that is no longer used.

[matiasbenedetto]

What?

Remove WP_Font_Family class and its tests.

Why?

Because it's no longer used after #57688

How?

Removing the source code file and its tests.

Testing Instructions

• Run unit tests
• Use the font library and check everything works as expected.

[github-actions]

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/load.php

[github-actions]

Flaky tests detected in 6134d72.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/7640757532
📝 Reported issues:

• [Flaky Test] Only the first block is an empty paragraph block #58161 in /test/e2e/specs/editor/blocks/paragraph.spec.js

[pbking]

The Font Library continues to work as expected. Unit tests continue to pass.

This change looks good to me.

[getdave]

I noticed this PR was merged after I raised the PHP Sync Tracking Issue for WP 6.5 and has changed PHP files that may need backporting to WP Core.

I believe this will be backported as part of a single backport for the Fonts API. It's been added to the Tracking Issue.

[cbravobernal]

This PR was already in release/17.6, it seems that there is no need to backport it. @creativecoder

[creativecoder]

Thanks @c4rl0sbr4v0 for checking! We had a number of smaller font library PRs to touch things up in the last week, I wasn't sure which ones made it into the rc or not.