Add view config API and endpoint

[oandregal]

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

What?

Introduces a server-side, filterable API for the DataViews/DataForm configuration of an entity, plus a REST endpoint that exposes it.

• wp_get_entity_view_config( $kind, $name ) (new src/wp-includes/view-config.php) builds the shared defaults (default view, layouts, view list, form) and runs them through a dynamic get_entity_view_config_{$kind}_{$name} filter so core and plugins can provide per-entity configuration.
• Core registers default providers for the page, post, wp_block, wp_template_part, and wp_template post types as filter callbacks on init (_wp_get_entity_view_config_post_type_*).
• WP_REST_View_Config_Controller exposes the config at GET /wp/v2/view-config?kind=…&name=…, delegating to the API and handling REST concerns (schema, edit_posts permission, empty-object serialization).
• Adds PHPUnit coverage for both the API and the controller.

Why?

Part of WordPress/gutenberg#76544

How?

Backports the View Config REST API endpoint from Gutenberg to WordPress Core.

• Site Editor > Pages: move view config to the server gutenberg#76573
• Site Editor > Patterns: move config to the server gutenberg#76734
• Site Editor > Templates: move config to the server gutenberg#76622
• Site Editor > Patterns & Parts: generate sidebar from view config gutenberg#76823
• Site Editor > Quick Edit: add form config to endpoint gutenberg#76953
• Fields: Tweak excerpt field gutenberg#76903
• Fix Gutenberg_REST_View_Config_Controller_7_1 PHP warnings gutenberg#77290
• Extract entity view config into a filterable API gutenberg#78977
• Experiment: Editor Inspector with DataForm - remove revision panel and add link gutenberg#79195
• Experimental: Expand Editor Inspector: Use DataForm experiment to templates gutenberg#76934
• View Config API and REST Endpoint: make them core ready gutenberg#79347
• Experimental: Expand Editor Inspector: Use DataForm experiment to template parts gutenberg#79399

Testing Instructions

1. Start a WordPress development environment.
2. Log in as an admin user.
3. Send a GET request to /wp-json/wp/v2/view-config?kind=postType&name=post — verify it returns generic defaults (table view, author/status fields).
4. Send a GET request to /wp-json/wp/v2/view-config?kind=postType&name=page — verify it returns page-specific config (list view, status sub-views like Published, Drafts, Trash).
5. Send the same request as an unauthenticated user — verify it returns a rest_cannot_read error.

You may want to send a GET request from the console, after having logged in into wp-admin:

fetch('http://localhost:8889/wp-json/wp/v2/view-config?kind=postType&name=post', {
    headers:{
        'X-WP-Nonce': wpApiSettings.nonce
    }
})
  .then(res => res.json())
  .then(console.log)

Use of AI Tools

This backport was prepared with the assistance of Claude Code (Claude Opus 4.8).

[github-actions]

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.

[github-actions]

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 oandregal, ntsekouras.

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

[Copilot]

Pull request overview

Introduces a new core API for retrieving an entity’s DataViews/DataForm view configuration and exposes it via a new REST endpoint, including PHPUnit coverage for both the API and endpoint behavior.

Changes:

• Added wp_get_entity_view_config( $kind, $name ) and default per-post-type providers registered on init.
• Added WP_REST_View_Config_Controller exposing GET /wp/v2/view-config?kind=…&name=… with schema + permission handling and JSON object serialization for empty object-shaped values.
• Added PHPUnit tests for the API and the REST controller.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
tests/phpunit/tests/view-config.php	Adds unit tests for the new view-config API defaults and filter behavior.
tests/phpunit/tests/rest-api/rest-view-config-controller.php	Adds REST API tests for routing, permissions, required params, schema shape, and object serialization.
src/wp-settings.php	Loads the new view-config API file and REST controller class during bootstrap.
src/wp-includes/view-config.php	Implements the new API and core default providers for several post types.
src/wp-includes/rest-api/endpoints/class-wp-rest-view-config-controller.php	Adds REST controller exposing the view-config via wp/v2/view-config with schema.
src/wp-includes/rest-api.php	Registers the new controller’s routes in initial REST route setup.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[ntsekouras]

LGTM, thanks!

[github-actions]

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

SVN changeset: 62547
GitHub commit: 36cc6e9

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