-
Notifications
You must be signed in to change notification settings - Fork 440
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
Schema default value not used #40
Comments
Actually, looking a bit more, it seems like putting an example parameter value for a header is not supported in OpenAPI v2 (see this thread). Then I'm eagerly awaiting this issue to be resolved! |
Hello, Your example is wrong because in OpenAPI 2.0, parameters can only have a With that said, |
A quick read over this could maybe clear up a bit more stuff. Will also look into adding more assertions against using wrong combinations of attributes like this. |
Related to the OpenAPI 3 issue - as stated in its text, it won't likely be resolved in the near future (few months at least), since most 3rd party tools have no support for the interesting new features or even the 3.0 spec itself. |
Trying to set a default value for a Schema inside of a Parameter. It does not seem to be getting picked up in Swagger when I use the "Try it out" functionality.
My schema looks like this:
Perhaps providing a more in depth example in testproj, that uses more of the OpenApi parameters, would be helpful. From what I read here it seems the example field should be used rather than default, but it does not seem to be an available field in the Schema class?
The text was updated successfully, but these errors were encountered: