-
Notifications
You must be signed in to change notification settings - Fork 270
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
Parameters no longer show their defaults #226
Comments
hey @chaosk, there was no intended change there as far as i remember. i'll have to investigate. |
From the looks of it, it was this change: 50eff74#diff-d727722caf6fe5f5507940c9efbcbe843fcca1dec9ac64402f074b08dd1c294fR250 |
ahh thx, good catch. i'll try to remedy that. |
tfranzel
added a commit
that referenced
this issue
Dec 8, 2020
@chaosk the original behavior should be largely restored with that change. |
Thank you for quick fix! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello!
Starting with 0.9.14, all parameters ignore certain attributes, such as
default
. Previously this only affected path parameters (since they must be required, a default value doesn't make much sense).Describing defaults for query params seems very useful to show how API behaves when not provided with a parameter value.
Would it be possible to bring back previous behavior, or at least make it easier to customize?
The text was updated successfully, but these errors were encountered: