-
-
Notifications
You must be signed in to change notification settings - Fork 273
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build setting allParamsOptional is not working as expected #1322
Comments
@wouterkroes if you want to investigate and provide a PR that would be great! |
@melloware I gave it a try, #1361, what do you think? |
I think this is by design. The query can't be enabled without those params, because they are path params (they go into URL like For us it doesn't make sense to be passing null or undefined values in there, so this is the reason for this feature to exist. To fix this issue you can rename For other stuff it doesn't make sense to make them optional. Your swagger schema should define which properties are required, and which are optional. If it doesn't match reality - fix the BE to generate correct schema for your FE. If you really need it - please create a separate flag, because this one isn't it. Hopefully I remembered everything correctly, but feel free to double check. Hope this helps, cheers! |
What are the steps to reproduce this issue?
What happens?
Not all params are optional.
What were you expecting to happen?
All params are optional.
Any logs, error output, etc?
No
Any other comments?
Generated output
My guess is that params of type Object (and Array?) are not handled correctly.
What versions are you using?
Operating System: Windows
Package Version: 6.27.1
Browser Version: n/a
The text was updated successfully, but these errors were encountered: