REST API: Allow null template origin - #13294
Conversation
|
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 Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Test using WordPress PlaygroundThe 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
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
Description
The REST API schema for the
originproperty of thewp/v2/template-partsendpoint currently declares the value as a string.However,
WP_Block_Template::origincan also returnnull, so the schema does not accurately describe the actual REST API response.This change updates the
originschema to accept bothstringandnullvalues.Trac ticket: https://core.trac.wordpress.org/ticket/64168
Testing
WP_REST_Templates_Controllerpass.Use of AI Tools
AI assistance: Yes
Tool(s): ChatGPT
Model(s): GPT-5.6 Luna
Used for: Reviewing the proposed change, discussing the implementation and test approach, and troubleshooting the Git/GitHub contribution workflow. The final code change was reviewed and tested 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.