Opened 8 months ago
Closed 7 days ago
#63166 closed task (blessed) (fixed)
Docblock improvements for WP 6.9
| Reported by: | | Owned by: | |
|---|---|---|---|
| Milestone: | 6.9 | Priority: | normal |
| Severity: | normal | Version: | |
| Component: | General | Keywords: | has-patch |
| Focuses: | coding-standards | Cc: |
Description
Change History (73)
This ticket was mentioned in PR #8806 on WordPress/wordpress-develop by @johnbillion.
6 months ago #8
- Keywords has-patch added
@johnbillion commented on PR #8806:
6 months ago #10
This ticket was mentioned in PR #8837 on WordPress/wordpress-develop by @johnbillion.
6 months ago #11
The @internal tag is an odd one, it has a different meaning depending on whether it's used as a top-level tag or an inline tag. Quoting the phpDocumentor docs:
The
@internaltag is used to denote that associated _Structural Elements_ are internal to the application or library. It may also be used inside a long description to insert a piece of text that is only applicable for the developers of the software.
So the former denotes that the symbol is for internal use only, and the latter denotes some internal documentation.
This PR fixes some instances of top level @internal tags that should be inline tags.
- Trac ticket: https://core.trac.wordpress.org/ticket/63166
- See https://github.com/php-stubs/wordpress-stubs/issues/287 CC @szepeviktor @jcvignoli.
@johnbillion commented on PR #8837:
6 months ago #13
This ticket was mentioned in PR #9100 on WordPress/wordpress-develop by @jonsurrell.
5 months ago #20
While working on PR 9099, I discovered the valid_unicode function and was curious about the set of codepoints it allows.
"Valid unicode" does not seem self explanatory, however after discussion with @dmsnell and looking at the history,
it appears that this follows the XML definition of a valid unicode character. This is now references in the function
docblock. Additionally, the separate conditions are also documented to clarify how they correspond to each part of
the XML valid unicode character description.
The hexadecimal literals are capitalized to match the quoted specification.
Trac ticket: https://core.trac.wordpress.org/ticket/63166
This ticket was mentioned in PR #9124 on WordPress/wordpress-develop by @johnbillion.
5 months ago #21
MySQL isn't the only supported database server, so this updates docs and one i18n string to use more generic terminology.
- Trac ticket: https://core.trac.wordpress.org/ticket/63166
- Trac ticket: https://core.trac.wordpress.org/ticket/60037
@johnbillion commented on PR #9124:
5 months ago #23
Committed in https://core.trac.wordpress.org/changeset/60363
@jonsurrell commented on PR #9100:
5 months ago #25
Merged in [60405].
This ticket was mentioned in PR #9202 on WordPress/wordpress-develop by @shailu25.
4 months ago #27
Trac ticket: https://core.trac.wordpress.org/ticket/63166
Corrected @since Order in Inline Documents in Below Files:
- src/wp-admin/includes/class-wp-screen.php
- src/wp-admin/includes/misc.php
- src/wp-admin/includes/template.php
@mukesh27 commented on PR #9202:
4 months ago #28
@SergeyBiryukov These one is ready for commit.
@shailu25 commented on PR #9202:
3 months ago #33
Rebased with Latest Trunk.
@shailu25 commented on PR #9202:
3 months ago #37
Merged in 60658
This ticket was mentioned in PR #9679 on WordPress/wordpress-develop by @rollybueno.
3 months ago #39
Per the PHP manual, if a function omits return, the value null is returned.
wp_ext2type() either returns a string for known extensions or null when no match is found. The doc block is updated to reflect this: string|null.
Trac ticket: https://core.trac.wordpress.org/ticket/63166
This ticket was mentioned in PR #9680 on WordPress/wordpress-develop by @rollybueno.
3 months ago #40
This function returns the first matching file extension (e.g. 'jpg' for 'image/jpeg') or false if no match is found. The return description has been updated for clarity.
Trac ticket: https://core.trac.wordpress.org/ticket/63166
@SergeyBiryukov commented on PR #9679:
3 months ago #41
Thanks for the PR!
In core, I think we generally use null in the @return tag when the function has an explicit return null line. Otherwise, we use void, which is the case here. So it seems like this change would be inconsistent with the rest of core.
That said, we could perhaps reconsider this, but ideally in a consistent way 🙂
@SergeyBiryukov commented on PR #9680:
3 months ago #43
Thanks for the PR! Merged in r60696.
This ticket was mentioned in PR #9743 on WordPress/wordpress-develop by @rollybueno.
2 months ago #44
Add descriptive text for @param and @return tags for standardization. No functional changes.
Trac ticket: https://core.trac.wordpress.org/ticket/63166
@rollybueno commented on PR #9679:
2 months ago #45
Thanks. Closing here then, we can think about that sometime in the future.
This ticket was mentioned in PR #9744 on WordPress/wordpress-develop by @rollybueno.
2 months ago #46
Add descriptive text for @param and @return tags for standardization.
Trac ticket: https://core.trac.wordpress.org/ticket/63166
@SergeyBiryukov commented on PR #9743:
2 months ago #48
Thanks for the PR! Merged in r60709.
@SergeyBiryukov commented on PR #9744:
2 months ago #50
Thanks for the PR! Merged in r60714.
@SergeyBiryukov commented on PR #9773:
2 months ago #52
Thanks for the PR! Merged in r60724.
This ticket was mentioned in PR #9821 on WordPress/wordpress-develop by @mukesh27.
2 months ago #53
Trac ticket: https://core.trac.wordpress.org/ticket/63166
@SergeyBiryukov commented on PR #9821:
2 months ago #55
Thanks for the PR! Merged in r60730.
This ticket was mentioned in PR #9947 on WordPress/wordpress-develop by @mukesh27.
2 months ago #56
Trac ticket: https://core.trac.wordpress.org/ticket/63166
@SergeyBiryukov commented on PR #9947:
2 months ago #59
Thanks for the PR! Merged in r60780.
This ticket was mentioned in PR #9970 on WordPress/wordpress-develop by @shailu25.
2 months ago #60
Added @see tag before @param tag in Inline Documentation:
- src/wp-includes/class-wp-customize-widgets.php
Trac ticket: #63166
@SergeyBiryukov commented on PR #9970:
7 weeks ago #62
Thanks for the PR! Merged in r60802.
This ticket was mentioned in PR #10247 on WordPress/wordpress-develop by @mukesh27.
5 weeks ago #65
Trac ticket: https://core.trac.wordpress.org/ticket/63166
@SergeyBiryukov commented on PR #10247:
5 weeks ago #67
Thanks for the PR! Merged in r60938.
This ticket was mentioned in Slack in #core by welcher. View the logs.
7 days ago
#73
@
7 days ago
- Resolution set to fixed
- Status changed from new to closed
With RC1 in less than 24 hours and the branching of 6.9 immanent, I've created #64224 for the 7.0 release and will close this one out.
If there are further changes required for 6.9, this can be reopened or referenced in the commit message.
In 60109: