summaryrefslogtreecommitdiffstatshomepage
path: root/tests/phpunit/includes/phpunit7
diff options
context:
space:
mode:
authorTimothy Jacobs <timothyblynjacobs@git.wordpress.org>2020-09-05 21:50:31 +0000
committerTimothy Jacobs <timothyblynjacobs@git.wordpress.org>2020-09-05 21:50:31 +0000
commitd803f6bf8228625a384dbb694337c7d7957f1ec3 (patch)
treea9594afc865e6749b61f45e1bc12d0a2078f663e /tests/phpunit/includes/phpunit7
parent1c1a7b83650181fb11d6925aeac6c0482020f865 (diff)
downloadwordpress-d803f6bf8228625a384dbb694337c7d7957f1ec3.tar.gz
wordpress-d803f6bf8228625a384dbb694337c7d7957f1ec3.zip
REST API: Refactor `WP_REST_Server::dispatch()` to make internal logic reusable.
#50244 aims to introduce batch processing in the REST API. An important feature is the ability to enforce that all requests have valid data before executing the route callbacks in "pre-validate" mode. This necessitates splitting `WP_REST_Server::dispatch()` into two methods so the batch controller can determine the request handler to perform pre-validation and then respond to the requests. The two new methods, `match_request_to_handler` and `respond_to_request`, have a public visibility, but are marked as `@access private`. This is to allow for iteration on the batch controller to happen in the Gutenberg repository. Developers should not rely upon these methods, their visibility may change in the future. See #50244. Props andraganescu, zieladam, TimothyBlynJacobs. git-svn-id: https://develop.svn.wordpress.org/trunk@48947 602fd350-edb4-49c9-b593-d223f7449a82
Diffstat (limited to 'tests/phpunit/includes/phpunit7')
0 files changed, 0 insertions, 0 deletions