Fixes typo in class PHPDoc comment #47261
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alexstine
added
the
[Type] Code Quality
aristath
approved these changes
Jan 19, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
In the process of looking into the new webfonts functionality I noticed a typo in the PHPDoc comment for the class
WP_Webfonts_ProviderWhy?
This PR would update the method in the comment from "set_setfonts" to "set_fonts" to match the function name within the class.
How?
This PR addresses the issue by updating the doc comment with the correct method name. This was not a code change/will not change any functionality.
Testing Instructions
To test this verify that the updated method name matches the method in the class that is being discussed. The method
set_setfontsdoes not exist and the method is namedset_fonts.Testing Instructions for Keyboard
This is a comment level change and not a visual change on the front end/gutenberg plugin functionality. This keyboard testing instruction may not apply for this small comment change.