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 am using kinopenapi version 0.110.0,
If the schema contains parameters with a default value, and those parameters are missing in the request, then kinopenapi adds the
default values to the request after the validation.
This is not the desired behavior (in some cases) when the validation takes place on the client side.
This is because of the following reasons:
The payload is unnecessarily larger.
The server may respond differently if the default value exists.
So, the already existing SkipSettingDefaults option should be used for query parameters as well.
I will create a pull request to handle this issue.
Thanks,
Oren
The text was updated successfully, but these errors were encountered:
Hi,
I am using kinopenapi version 0.110.0,
If the schema contains parameters with a default value, and those parameters are missing in the request, then kinopenapi adds the
default values to the request after the validation.
This is not the desired behavior (in some cases) when the validation takes place on the client side.
This is because of the following reasons:
So, the already existing
SkipSettingDefaults
option should be used for query parameters as well.I will create a pull request to handle this issue.
Thanks,
Oren
The text was updated successfully, but these errors were encountered: