Skip to content

Jsdoc r63766 follow-up - #13650

Closed
afercia wants to merge 2 commits into
WordPress:trunkfrom
afercia:jsdoc-r63766-followup
Closed

Jsdoc r63766 follow-up#13650
afercia wants to merge 2 commits into
WordPress:trunkfrom
afercia:jsdoc-r63766-followup

Conversation

@afercia

@afercia afercia commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

Follow-up to #13486

See https://core.trac.wordpress.org/ticket/66033

Use of AI Tools

This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

@github-actions

github-actions Bot commented Sep 22, 2026

Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props afercia.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@afercia afercia changed the title Jsdoc r63766 followup Jsdoc r63766 follow-up Sep 22, 2026
@github-actions

github-actions Bot commented Sep 22, 2026

Copy link
Copy Markdown

Test using WordPress Playground

The 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

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

wporg-sync pushed a commit that referenced this pull request Sep 22, 2026
@afercia
General: Better documentation for the sync functions in the wp api.js…
c096156 
… file.

Amends [63766]. Better document the options param and return tag for the `sync` functions in `src/js/_enqueues/wp/api.js`.

Part of the effort to improve JS inline documentation for 7.2.

Developed in #13650

Props westonruter, afercia.
See #66033.


git-svn-id: https://develop.svn.wordpress.org/trunk@63791 602fd350-edb4-49c9-b593-d223f7449a82
wporg-sync pushed a commit to WordPress/WordPress that referenced this pull request Sep 22, 2026
@afercia
General: Better documentation for the sync functions in the wp api.js…
b813b42 
… file.

Amends [63766]. Better document the options param and return tag for the `sync` functions in `src/js/_enqueues/wp/api.js`.

Part of the effort to improve JS inline documentation for 7.2.

Developed in WordPress/wordpress-develop#13650

Props westonruter, afercia.
See #66033.

Built from https://develop.svn.wordpress.org/trunk@63791


git-svn-id: http://core.svn.wordpress.org/trunk@62963 1a063a9b-81f0-0310-95a4-ce76da25c4cd
@afercia

afercia commented Sep 22, 2026

Copy link
Copy Markdown
Contributor Author

Committed in https://core.trac.wordpress.org/changeset/63791

@afercia afercia closed this Sep 22, 2026
@afercia
afercia deleted the jsdoc-r63766-followup branch September 22, 2026 07:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@afercia