mirrored from git://develop.git.wordpress.org/
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
HTML API: Fix phpdoc nullable types #7031
Closed
sirreal
wants to merge
3
commits into
WordPress:trunk
from
sirreal:html-api/fix-nullable-phpdoc-annotations
Closed
HTML API: Fix phpdoc nullable types #7031
sirreal
wants to merge
3
commits into
WordPress:trunk
from
sirreal:html-api/fix-nullable-phpdoc-annotations
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
Test using WordPress PlaygroundThe changes in this pull request can previewed and tested using a WordPress Playground instance. WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser. Some things to be aware of
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
sirreal
changed the title
HTML API: Fix phpdoc nullable types'
HTML API: Fix phpdoc nullable types
Jul 15, 2024
19 tasks
pento
pushed a commit
that referenced
this pull request
Jul 17, 2024
It was found that in several places in the HTML API and its supporting files, the wrong form of type annotation was used for optional parameters. Instead of using `?type`, this patch uses `type|type-of-default-value` instead, noting where important if the parameter is optional, and if so, what its default value is. Developed in #7031 Discussed in https://core.trac.wordpress.org/ticket/61399 Props dmsnell, jonsurrell. See #61399. git-svn-id: https://develop.svn.wordpress.org/trunk@58742 602fd350-edb4-49c9-b593-d223f7449a82
markjaquith
pushed a commit
to markjaquith/WordPress
that referenced
this pull request
Jul 17, 2024
It was found that in several places in the HTML API and its supporting files, the wrong form of type annotation was used for optional parameters. Instead of using `?type`, this patch uses `type|type-of-default-value` instead, noting where important if the parameter is optional, and if so, what its default value is. Developed in WordPress/wordpress-develop#7031 Discussed in https://core.trac.wordpress.org/ticket/61399 Props dmsnell, jonsurrell. See #61399. Built from https://develop.svn.wordpress.org/trunk@58742 git-svn-id: http://core.svn.wordpress.org/trunk@58144 1a063a9b-81f0-0310-95a4-ce76da25c4cd
github-actions bot
pushed a commit
to platformsh/wordpress-performance
that referenced
this pull request
Jul 17, 2024
It was found that in several places in the HTML API and its supporting files, the wrong form of type annotation was used for optional parameters. Instead of using `?type`, this patch uses `type|type-of-default-value` instead, noting where important if the parameter is optional, and if so, what its default value is. Developed in WordPress/wordpress-develop#7031 Discussed in https://core.trac.wordpress.org/ticket/61399 Props dmsnell, jonsurrell. See #61399. Built from https://develop.svn.wordpress.org/trunk@58742 git-svn-id: https://core.svn.wordpress.org/trunk@58144 1a063a9b-81f0-0310-95a4-ce76da25c4cd
Debarghya-Banerjee
pushed a commit
to Debarghya-Banerjee/wordpress-develop
that referenced
this pull request
Jul 18, 2024
It was found that in several places in the HTML API and its supporting files, the wrong form of type annotation was used for optional parameters. Instead of using `?type`, this patch uses `type|type-of-default-value` instead, noting where important if the parameter is optional, and if so, what its default value is. Developed in WordPress#7031 Discussed in https://core.trac.wordpress.org/ticket/61399 Props dmsnell, jonsurrell. See #61399. git-svn-id: https://develop.svn.wordpress.org/trunk@58742 602fd350-edb4-49c9-b593-d223f7449a82
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-61399