Feature: Expose post_types field to Templates REST API

[Debarghya-Banerjee]

Trac Ticket: Core-61308

Overview

This pull request adds a new post_types field to the existing WordPress REST API endpoint for templates (/wp/v2/templates). This enhancement allows users to filter templates based on the post types they are intended for, thereby improving usability and functionality in the site editor templates screen.

Changes Made

Modified get_item_schema():

• Added a new property, post_types, to the JSON schema for templates.

• The post_types field is defined as an array of strings, describing the associated post types for each template.

Updated prepare_item_for_response():

• Implemented logic to fetch and include the post_types information in the API response.

• Ensured that the post_types field is populated based on the associated post types stored in the template's metadata.

Benefits

• Improved Filtering: Users can now filter templates directly by their associated post types, making it easier to find relevant templates for specific content types.

• Enhanced API Usability: By exposing the post_types field, we align the API capabilities with user expectations and common use cases.

[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 debarghyabanerjee.

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

[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

• The Plugin and Theme Directories cannot be accessed within Playground.
• 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.