Opened 22 months ago
Closed 17 months ago
#57840 closed task (blessed) (fixed)
Docblock improvements for 6.3
Reported by: | hellofromTonya | Owned by: | |
---|---|---|---|
Milestone: | 6.3 | Priority: | normal |
Severity: | normal | Version: | |
Component: | General | Keywords: | has-patch dev-reviewed commit |
Focuses: | docs, coding-standards | Cc: |
Attachments (3)
Change History (93)
This ticket was mentioned in PR #4347 on WordPress/wordpress-develop by SweetSue.
20 months ago
#2
- Keywords has-patch added
#4
@
20 months ago
Hi there, just noting that we are at WordCamp Paris contributor day right now, and we're going to use small Docblock changes to onboard people on the contribution process to Core :)
This ticket was mentioned in PR #4348 on WordPress/wordpress-develop by lmag.
20 months ago
#5
@audrasjb commented on PR #4347:
20 months ago
#9
committed in https://core.trac.wordpress.org/changeset/55664
This ticket was mentioned in PR #4350 on WordPress/wordpress-develop by SweetSue.
20 months ago
#10
This ticket was mentioned in PR #4351 on WordPress/wordpress-develop by JBCouton.
20 months ago
#11
@audrasjb commented on PR #4351:
20 months ago
#14
Committed in https://core.trac.wordpress.org/changeset/55681
@audrasjb commented on PR #4350:
20 months ago
#15
Committed in https://core.trac.wordpress.org/changeset/55681
@audrasjb commented on PR #4348:
20 months ago
#16
Committed in https://core.trac.wordpress.org/changeset/55681
@audrasjb commented on PR #4348:
20 months ago
#17
Committed in https://core.trac.wordpress.org/changeset/55681
This ticket was mentioned in PR #4419 on WordPress/wordpress-develop by @johnbillion.
20 months ago
#22
Trac ticket: https://core.trac.wordpress.org/ticket/57840
There's many helpful code examples in the docs for the WP_HTML_Tag_Processor
class but they're all indented by four unnecessary spaces. They use the <code>`php</code> wrapper which makes the indentation appear in the code blocks on the developer reference site. This fixes that by removing the extraneous indentation.
There's also an additional fix for the note about the U+FFFD
character.
Example URLs that display the unnecessary indentation:
This ticket was mentioned in PR #4420 on WordPress/wordpress-develop by @johnbillion.
20 months ago
#25
Trac ticket: https://core.trac.wordpress.org/ticket/57840
@johnbillion commented on PR #4419:
20 months ago
#27
@johnbillion commented on PR #4420:
20 months ago
#29
20 months ago
#30
Thanks @johnbillion - I was under the impression the indentation was required, but I've double-checked after this change and the code still renders as code at least in PHPStorm and VSCode.
@johnbillion commented on PR #4419:
20 months ago
#32
I was under the impression the indentation was required
Yeah you just need either the backticks or the indentation but not both 😄
what was wrong with the U+FFFD note?
It was just to remove the unprintable character from the source code 👍
looks right to me in the linked documentation
Yeah the docs on the developer reference site only get regenerated from the source when each new version of WordPress is released
20 months ago
#33
but not both
ahaa
It was just to remove the unprintable character from the source code 👍
that character _is_ printable though, and it printed
maybe it's confusing because _that character_ is the character used _when the string has invalid characters in it_?
I think maybe it was a mistake to remove. we added that originally to show what it is, thinking people would more readily recognize � than U+FFFD
@johnbillion commented on PR #4419:
20 months ago
#34
Ohhhh _that_ is the actual unicode character displayed as a replacement when a character is unprintable? I see.
20 months ago
#35
@johnbillion do you have any thoughts about me adding it back in? maybe surround it in quotes this time to try and make it more obvious that it's the actual character?
sorry this wasn't caught in review. I would have noted it, but the PR was created and merged before I was still asleep
#44
follow-up:
↓ 46
@
19 months ago
@SergeyBiryukov do you mind backporting the changes you made to the HTML API to Gutenberg? every update in Core needs to be followed by such a change so the two sides don't get out of sync. I'm happy to review/approve the "blessed" PR over there for you.
#46
in reply to:
↑ 44
;
follow-up:
↓ 50
@
19 months ago
Replying to dmsnell:
do you mind backporting the changes you made to the HTML API to Gutenberg? every update in Core needs to be followed by such a change so the two sides don't get out of sync.
I was not aware of that, thanks! Sure, will create a PR :)
#47
@
19 months ago
More 'a' => 'an' candidates:
\src\wp-admin\includes\class-bulk-upgrader-skin.php
Line 82: Nothing, This will be displayed within a iframe.
\src\wp-admin\includes\class-pclzip.php
Line 637: read_error : the file was not extracted because there was a error
\src\wp-admin\includes\file.php
Line 1380: Check for a edge-case affecting PHP Maths abilities.
\src\wp-includes\class-wp-http-cookie.php
Line 139: Handle the cookie ending in ; which results in a empty final pair.
\src\wp-includes\class-wp-http.php
Line 1083: * '4' or '6' to represent a IPv4 and IPv6 address respectively.
\src\wp-includes\class-wp-oembed.php
Line 517: * Connects to a oEmbed provider and returns the result.
\src\wp-includes\media-template.php
Line 11: * Outputs the markup for a audio tag to be used in an Underscore template
\src\wp-includes\media.php
Line 4814: * Checks the HTML content for a audio, video, object, embed, or iframe tags.
\src\wp-includes\option.php
Line 1373: * Removes a option by name for the current network.
\src\wp-includes\Requests\src\IdnaEncoder.php
Line 29: * Maximum length of a IDNA URL in ASCII.
\src\wp-includes\customize\class-wp-customize-nav-menu-item-setting.php
Line 231: Note that a ID of less than one indicates a nav_menu not yet inserted.
#50
in reply to:
↑ 46
@
19 months ago
Replying to SergeyBiryukov:
Replying to dmsnell:
do you mind backporting the changes you made to the HTML API to Gutenberg? every update in Core needs to be followed by such a change so the two sides don't get out of sync.
I was not aware of that, thanks! Sure, will create a PR :)
Thanks @SergeyBiryukov - you can use #48812 as an example.
This workflow is the result of developing the work in Core first and keeping Gutenberg in sync, since that seems to be how everyone prefers it, and since it's easier getting these updates into the plugin (we just need to make sure we do that).
Feel free to add me as a reviewer.
This ticket was mentioned in PR #4551 on WordPress/wordpress-develop by @costdev.
19 months ago
#54
Trac ticket: https://core.trac.wordpress.org/ticket/57840
This ticket was mentioned in PR #4552 on WordPress/wordpress-develop by @costdev.
19 months ago
#55
Trac ticket: https://core.trac.wordpress.org/ticket/57840
@audrasjb commented on PR #4551:
18 months ago
#61
Added a commit to resolve a conflict.
@audrasjb commented on PR #4552:
18 months ago
#63
Thanks for the update!
Committed in https://core.trac.wordpress.org/changeset/55911
@audrasjb commented on PR #4551:
18 months ago
#67
@
18 months ago
Twenty Seventeen: correcting a typo and removing a word that never belongs in documentation (props mukesh27)
@
17 months ago
The $data
parameter in WP_REST_Attachments_Controller::upload_from_data()
is passed and treated only as string
, not array
.
In 55539: