HTML API: Fix typo in documentation example. #5661
Closed
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
Trac ticket: Core-59891 Resolves: WordPress/Documentation-Issue-Tracker#1362 The example code in the PHPDoc comment for the HTML Tag Processor class previously showed calling `next_tag()` with an array containing a `class` key, which should have been `class_name`. This patch fixes this by using the appropriate `class_name` key. Props: @gaambo, @crstauf, @atachibana
audrasjb
approved these changes
Nov 11, 2023
krupal-panchal
approved these changes
Nov 13, 2023
|
Committed to Core in https://core.trac.wordpress.org/changeset/57116. |
|
Backported to Core's 6.4 branch in https://core.trac.wordpress.org/changeset/57117. |
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.
Trac ticket: Core-59891
Resolves: WordPress/Documentation-Issue-Tracker#1362
The example code in the PHPDoc comment for the HTML Tag Processor class previously showed calling
next_tag()with an array containing aclasskey, which should have beenclass_name. This patch fixes this by using the appropriateclass_namekey.Props: @gaambo, @crstauf, @atachibana
As a documentation change this should have no impact on any code and should need no testing.