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
I'm one of the developers of Flotiq, and we use this package to generate Postman collection dynamically after the user makes changes to their API, but it generates with one issue. We sometimes require only one element in an array (it is described in maxItems in the schema of the parameter), and it is validated on POST and PUT requests.
However, this package always generates an array with 2 sample elements in an array, it is connected with
Because of that when the user sends the POST or PUT request it sometimes results in an error (Too many elements).
I'm wondering why this is hardcoded like that, and if I can make it more dynamic and post PR with that change. Something like this
// This nonsense is needed because the schemaFaker doesn't respect options.maxItems/minItemsschema.maxItems=schema.maxItems??2;schema.minItems=schema.minItems??2;// have to create a shallow clone of schema object,
The text was updated successfully, but these errors were encountered:
Hello,
I'm one of the developers of Flotiq, and we use this package to generate Postman collection dynamically after the user makes changes to their API, but it generates with one issue. We sometimes require only one element in an array (it is described in maxItems in the schema of the parameter), and it is validated on POST and PUT requests.
However, this package always generates an array with 2 sample elements in an array, it is connected with
openapi-to-postman/lib/deref.js
Line 211 in 8e31ca7
Because of that when the user sends the POST or PUT request it sometimes results in an error (Too many elements).
I'm wondering why this is hardcoded like that, and if I can make it more dynamic and post PR with that change. Something like this
The text was updated successfully, but these errors were encountered: