A plugin can't change the parameters of a REST API endpoint

[antonvlasenko]

Sometimes a plugin needs to change the parameters of an already registered REST API endpoint.
Now we need to override the whole WP_REST_Controller::register_routes method to achieve it. Unfortunately, that leads to code duplication, and that is not the best practice.
See an example of this here: ​https://github.com/WordPress/gutenberg/blob/trunk/lib/class-wp-rest-menu-items-controller.php#L26.

We should add a new filter (add_filter) at the very beginning of the register_rest_route's function body. That filter must allow to modify all arguments of the register_rest_route function.

Add a register_route_args filter.

Trac ticket: https://core.trac.wordpress.org/ticket/54087

[spacedmonkey]

@TimothyBlynJacobs Can you provide any context here?

[TimothyBlynJacobs]

I don't have any context here, why this function was implemented without a filter was probably a very early decision.

Personally, I worry that such a low-level filter will get abused to add parameters to controllers without using the more intentional exposed APIs like register_rest_field.

I'm of the opinion that if controllers want to make portions of their route registration customizable, they should provide specific filters for that.

Gutenberg has pretty specialized needs as a place for prototyping features for Core, but I don't think we should be encouraging plugin developers to do the same.

[rachelbaker]

why this function was implemented without a filter was probably a very early decision.

@TimothyBlynJacobs is correct.

We intentionally avoided making it "easy" for plugins to have full control over the core endpoints. This design decision was made to favor standardization across all WP sites for the built-in endpoints. Plugins can easily extend existing endpoints or add new endpoints.