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
Example property on operations does not work #2767
Comments
Examples are not getting reflected in @ApiResponses. I am using springfox 2.9.2. Any idea when this will be fixed ? |
Same behaviour with 3.0.0-SNAPSHOT :( |
Any update of this? |
I am still facing problem with this, @example is not rendered even with 3.0.0-SNAPSHOT when it's just a week before it's getting released. |
Yes it should be, would love to see your feedback |
Looks like issue is not yet solved. Something to note though, even when I reimported my dependencies but it's still showing old value for jar - springfox-oas-3.0.0-SNAPSHOT.jar, it should be a newer value correct? Manifest-Version: 1.0 |
You need to force update your snapshot. |
We have lost the regular schema functionality though , other error codes expect @example also even though it can be easily inferred from its models but before this update it used come out like this . |
Thanks, I confirm after refreshing snapshot libraries @example annotation started working (check screenshot below) but it doesn't show schema object (as it shows in request body) in following screen shot |
Could you try using |
Yes I am using OAS-30 in my docket. @example annotation doesn’t work otherwise |
You clearly aren't using these 3.0 annotations |
what are the plans for releasing 3.0.0-SNAPSHOT into a official release? Where can I track if it's released? |
and the fields in Response class are annotated with
@ApiModelProperty(required = true, example = "Timeout exceeded")
then the example is also rendered. It's kind of a workaround, but also not an option in my case, because I need to use class provided by library and I can't annotate it.Originally posted by @tgielbutowicz in #2352 (comment)
The text was updated successfully, but these errors were encountered: