WordPress/wp-includes
desrosj 2785313bf2 REST API: Encourage proper usage of register_rest_route().
Calling `register_rest_route()` too early in the loading process has the potential to cause some unintentional problems and pitfalls. Because `register_rest_route()` calls `rest_get_server()` (which creates the `WP_REST_Server` instance), calling the function directly and/or before `rest_api_init` should be discouraged.

For example, if `register_rest_route ()` is called on `init`, the REST API server instance is set up (and all functions added to `rest_api_init` and other related hooks are invoked), even though the current request may not be a REST request. Also, if `register_rest_route()` is called even earlier (say, in an `mu-plugin` file), required endpoints may be missing since normal plugins have not yet been loaded and have not had a chance to register their own action hooks.

This adds a `_doing_it_wrong()` notice the first time `register_rest_route()` is called before `rest_api_init` in a request to encourage best practices for registering REST API routes.

Props kraftbj, desrosj, timothyblynjacobs.
Fixes #45265.
Built from https://develop.svn.wordpress.org/trunk@44568


git-svn-id: http://core.svn.wordpress.org/trunk@44399 1a063a9b-81f0-0310-95a4-ce76da25c4cd
2019-01-11 18:19:49 +00:00
..
2017-11-30 23:11:00 +00:00
2017-11-30 23:11:00 +00:00
2017-11-30 23:11:00 +00:00
2017-11-30 23:11:00 +00:00
2017-11-30 23:11:00 +00:00
2017-11-30 23:11:00 +00:00
2017-11-30 23:11:00 +00:00
2017-11-30 23:11:00 +00:00
2017-11-30 23:11:00 +00:00
2017-11-30 23:11:00 +00:00
2018-12-11 04:45:23 +00:00
2017-11-30 23:11:00 +00:00
2017-11-30 23:11:00 +00:00
2017-11-30 23:11:00 +00:00
2017-11-30 23:11:00 +00:00
2017-11-30 23:11:00 +00:00
2017-11-30 23:11:00 +00:00
2017-11-30 23:11:00 +00:00
2017-11-30 23:11:00 +00:00
2017-11-30 23:11:00 +00:00
2017-11-30 23:11:00 +00:00
2017-11-30 23:11:00 +00:00