Skip to content

Abilities API: Add public meta flag to control ability exposure defaults - #12463

Closed
Adi-ty wants to merge 2 commits into
WordPress:trunkfrom
Adi-ty:add/65568-abilities-meta-public-flag
Closed

Abilities API: Add public meta flag to control ability exposure defaults#12463
Adi-ty wants to merge 2 commits into
WordPress:trunkfrom
Adi-ty:add/65568-abilities-meta-public-flag

Conversation

@Adi-ty

@Adi-ty Adi-ty commented Jul 9, 2026 •
edited
Loading

Copy link
Copy Markdown

Introduce a public flag in ability metadata as a single high-level control over client exposure. When set, public seeds the default for show_in_rest via null coalescing:
show_in_rest = meta'show_in_rest' ?? meta'public' ?? false

An explicit show_in_rest: false always wins over public: true, preserving per-channel opt-out. The public key stays in stored metadata so other channels (MCP, AI agents) can read it via the wp_register_ability_args filter.

Testing: npm run test:php -- --group abilities-api --filter 'public'

Trac ticket: https://core.trac.wordpress.org/ticket/65568

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.

@Adi-ty
Abilities API: Add public meta flag to control ability exposure def…
3fa9368 
…aults.

An explicit `show_in_rest` value wins over `public`, which wins over the
built-in default of `false`. The flag is stored only when provided and is
declared in the REST item schema.

See https://core.trac.wordpress.org/ticket/65568.
@github-actions

github-actions Bot commented Jul 9, 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.

@Adi-ty
Adi-ty marked this pull request as ready for review July 9, 2026 16:16
@github-actions

github-actions Bot commented Jul 9, 2026 •
edited
Loading

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 iamadisingh, gziolo.

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

gziolo
gziolo approved these changes Jul 14, 2026
View reviewed changes

@gziolo gziolo left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent, thank you for working on it.

@Adi-ty

Adi-ty commented Jul 14, 2026

Copy link
Copy Markdown
Author

Excellent, thank you for working on it.

Thanks for the review and approval! Glad to hear it.

@github-actions

github-actions Bot commented Jul 14, 2026

Copy link
Copy Markdown

A commit was made that fixes the Trac ticket referenced in the description of this pull request.

SVN changeset: 62729
GitHub commit: a1d2d15

This PR will be closed, but please confirm the accuracy of this and reopen if there is more work to be done.

@github-actions github-actions Bot closed this Jul 14, 2026
@gziolo gziolo mentioned this pull request Jul 14, 2026
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@gziolo gziolo gziolo approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@Adi-ty @gziolo