HTTP API: Add wp_remote_put(), wp_remote_delete(), wp_remote_patch() and safe variants - #12840
HTTP API: Add wp_remote_put(), wp_remote_delete(), wp_remote_patch() and safe variants#12840SainathPoojary wants to merge 2 commits into
Conversation
…and safe variants
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. |
…ote_{put,delete,patch}
|
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. |
Introduces helper functions for the remaining HTTP methods (
PUT,DELETE, andPATCH) to complement the existingwp_remote_get(),wp_remote_post(), andwp_remote_head()functions. This makes working with third-party APIs and the REST API much easier.The following wrapper functions have been added to
src/wp-includes/http.php:wp_remote_put()&wp_safe_remote_put()wp_remote_delete()&wp_safe_remote_delete()wp_remote_patch()&wp_safe_remote_patch()Trac ticket: #40142
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.