You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 24, 2018. It is now read-only.
Hi, I've got some logic in my pre_user_query and pre_get_posts that lets me use a custom value with the orderby query param.
In the latest update there's a breaking change that limits the valid request args to an enum set, and I understand I have to use rest_validate_request_arg somehow to allow my custom orderby value.
I don't know where/how to do this however, and if you could point me to the right filter or snippet that lets me merge my value with the defaults that would be great!
The text was updated successfully, but these errors were encountered:
In the latest update there's a breaking change that limits the valid request args to an enum set, and I understand I have to use rest_validate_request_arg somehow to allow my custom orderby value.
Sorry about that :( It skipped my mind that anyone would be using a custom orderby value.
I'll make sure we get the "extending routes" aspect documented WP-API/docs-v2#114
Hi, I've got some logic in my pre_user_query and pre_get_posts that lets me use a custom value with the orderby query param.
In the latest update there's a breaking change that limits the valid request args to an enum set, and I understand I have to use rest_validate_request_arg somehow to allow my custom orderby value.
I don't know where/how to do this however, and if you could point me to the right filter or snippet that lets me merge my value with the defaults that would be great!
The text was updated successfully, but these errors were encountered: