Testing: Entity actions, fields, and view configs together

[jorgefilipecosta]

Trac tickets: https://core.trac.wordpress.org/ticket/66343, https://core.trac.wordpress.org/ticket/65981

This PR combines three backport PRs and a Gutenberg pin update, so they can be tested together. It's for testing only, each piece is reviewed and committed in its own PR.

This PR:

• Includes Editor: Register the core entity fields on the server #14512, which registers the core entity fields on the server.
• Includes Editor: Register the core entity actions on the server #14509, which registers the core entity actions on the server.
• Includes Editor: Add the attachment entity view config for the media editor #14513, which adds the attachment view config, the form of the media editor.
• Pins Gutenberg to 2a96cb241e138e39035c5afbc65ec1ff5e2f6cb0, a trunk build that includes Core Actions, Core Fields: Translate the labels with the default text domain gutenberg#85139, and adds the files it copies over, including wp-includes/build/scripts/core-actions/ and wp-includes/build/scripts/core-fields/.

Some notes:

• The pin can't be the 24.2.0 one from General: Bump the pinned hash for Gutenberg to 7b95ee9. #14497: that release doesn't include Core Actions: Register the core actions on the server gutenberg#84660, Core fields: Register the default fields of WordPress on the server gutenberg#84696 or Editor: Read the entity fields from the server gutenberg#84700, so the actions and fields scripts aren't built and the new code registers nothing.
• Updates the view config endpoint with changes for WordPress 7.2 #14495 is needed because it adds _rest_cast_empty_objects_from_schema() to rest-api.php. The entity fields endpoint uses it to return empty objects as {} rather than [], as does the view config endpoint. It landed in r64503, so it's already in trunk and in the three PRs; nothing else to apply.
• With Core Actions, Core Fields: Translate the labels with the default text domain gutenberg#85139 in the pin, the labels are translated with the default text domain, so test_the_labels_are_translated_with_the_default_text_domain passes in the entity actions and in the entity fields tests.

Testing Instructions

1. Check out this branch and run npm run build:dev. The Gutenberg files are already committed.
2. Open wp-admin/site-editor.php?p=%2Fpage. Verify the list shows the page fields and the actions menu of a page works: rename, trash, restore and permanently delete. Do the same in the templates and patterns screens.
3. Open a post in the post editor and verify the fields and the actions menu in the inspector. Verify in the Network panel that the editor made no request to /wp/v2/entity-actions or /wp/v2/entity-fields, which are preloaded.
4. Insert an image block, click "Edit image" in its toolbar, then open the Details tab. Verify it shows the attachment fields from the view config.
5. Add the plugin below to wp-content/mu-plugins/. Verify "Copy title" and "Show details…" appear in the page list row menu, in the bulk bar (only "Copy title", which supports bulk) and in the post editor actions menu, and that both run.
6. Run npm run test:php -- --group entity-fields,entity-actions,view-config. Verify they pass.

Demo plugin: demo-entity-actions.php

<?php
/**
 * Plugin Name: Demo entity actions
 * Description: Registers two actions on posts and pages through the entity actions API.
 *
 * The PHP declares the serializable part of each action. The script module in
 * demo-entity-actions/actions.js provides the JavaScript parts, keyed by action id.
 */

add_action(
	'init',
	static function () {
		wp_register_script_module(
			'demo-entity-actions',
			plugins_url( 'demo-entity-actions/actions.js', __FILE__ ),
			array(),
			'1.0.1'
		);
	}
);

add_action(
	'wp_entity_actions_api_init',
	static function () {
		$actions = array(
			array(
				'id'           => 'demo-copy-title',
				'label'        => 'Copy title',
				'supportsBulk' => true,
			),
			array(
				'id'          => 'demo-details',
				'label'       => 'Show details…',
				'modalHeader' => 'Demo details',
			),
		);

		foreach ( array( 'post', 'page' ) as $post_type ) {
			wp_register_entity_actions( 'demo-entity-actions', 'postType', $post_type, $actions, 'demo-entity-actions' );
		}
	}
);

Demo plugin: demo-entity-actions/actions.js

/**
 * The JavaScript parts of the demo actions, keyed by the ids registered in PHP.
 */
const { createElement: el } = window.wp.element;
const {
	Button,
	__experimentalHStack: HStack,
	__experimentalVStack: VStack,
} = window.wp.components;

const getTitle = ( item ) =>
	( typeof item.title === 'string'
		? item.title
		: item.title?.raw ?? item.title?.rendered ) || `#${ item.id }`;

export default {
	'demo-copy-title': {
		callback: async ( items, { registry, onActionPerformed } ) => {
			const titles = items.map( getTitle ).join( '\n' );
			try {
				await window.navigator.clipboard.writeText( titles );
			} catch ( error ) {
				// The clipboard may be unavailable; the notice still shows the titles.
			}
			registry
				.dispatch( 'core/notices' )
				.createSuccessNotice( `Copied: ${ titles }`, {
					type: 'snackbar',
				} );
			onActionPerformed?.( items );
		},
	},
	'demo-details': {
		isEligible: ( item ) => item.status !== 'trash',
		RenderModal: ( { items, closeModal } ) =>
			el(
				VStack,
				{ spacing: 4 },
				el(
					'ul',
					null,
					items.map( ( item ) =>
						el(
							'li',
							{ key: item.id },
							`${ getTitle( item ) } — id ${ item.id }, ${ item.status }`
						)
					)
				),
				el(
					HStack,
					{ justify: 'flex-end' },
					el(
						Button,
						{ variant: 'primary', onClick: closeModal },
						'Close'
					)
				)
			),
	},
};

Use of AI Tools

AI assistance: Yes
Used for: combining the branches, staging the demo plugin, and drafting this description; reviewed and edited by me.

---

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]

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.

[oandregal]

Open a post in the post editor and verify the fields and the actions menu in the inspector. Verify in the Network panel that the editor made no request to /wp/v2/entity-actions or /wp/v2/entity-fields, which are preloaded.

For these instructions to work, the gutenberg sha should be e18c3cafbe1dc2f370fdc4cb7a44811766ea177c.

[github-actions]

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

SVN changeset: 64566
GitHub commit: a9398d7

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