POST /v1/entity/search endpoint for most entities. Internally, I use the search repository to handle other endpoints like GET /v1/entity and GET /v1/entity/:id. A general model for a Search body is HttpServerRequest.schemaSearchParams to add the same functionality to the /v1/entity?page=&limit=&field=&direction= endpoint) however, I'm not sure if I'm using the best model for extending them. I have a base SearchSchema whose fields I spread into another class that provides the match criteriasort.field to be keyof match which would be a nice default. So just looking for any feed back on that pattern