Missing pagination fields in UserSearchCriteria

[juliusbkh]

Description

The UserSearchCriteria object in the OpenAPI specification appears to be missing the pagination fields numberOfResults and startRow.

We are using a library generator, and these fields are not present in the generated Search Criteria object.
Parsing the OpenAPI.yml in tools like Swagger also indicates that the fields are not included.

The BaseSearchCriteria and BaseElasticSearchCriteria objects do contain the required fields, but neither of them is referenced in the specification.

Expected behavior

UserSearchCriteria should include the pagination properties numberOfResults and startRow, as supported by the API.

Additional context

We are aware that user searches can also be performed using the nextResults token.
However, having only the default page size of 25 can introduce noticeable overhead when iterating through larger user sets.

Including the pagination fields would help make these use cases more efficient.

[mooreds]

Interesting. This file is built using this script which looks at the JSON files here.

It sure looks like UserSearchCriteria "extends" BaseElasticSearchCriteria, so it should grab those extra fields and add them to the definition.

Will see if we can take a look.