Sieve and OpenAPI parameter validation errors

[esune]

My team is using Sieve to allow complex querying and filtering/sorting capabilities on our API endpoints. We are generating a swagger doc and are using the SwaggerUI successfully, however when being assessed on the "correctness" of the OpenAPI swagger document being generated we get a number of issues reported, such as:

• endpoint /my-endpoint have parameter 'Filters' (String) without the 'maxLength' property declared
• endpoint /my-endpoint have parameter 'Filters' (String) without the 'format' property declared
• endpoint /my-endpoint have parameter 'Sorts' (String) without the 'maxLength' property declared
• endpoint /my-endpoint have parameter 'Filters' (String) without the 'maxLength' property declared
  and so on.

I assume input validation is used on the parameters being submitted to the endpoint and was wondering what type of validation from this OWASP Cheat Sheet I vould/would indicate for Sieve as mitigating factor for this assessment.

Thanks!