-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Comments from XML Docs: not rendered for [FromForm] params #2519
Comments
I am also having this issue, except with the
I don't see any correlation in the model fields where the example is not rendered. It is seemingly random which fields generate correctly; however, the example is not rendered for the same fields consistently. I checked the documentation .xml file (not swagger.json) and I see the example tags are correct But in the swagger.json file generated schemas, these tags are not there for every model field. |
Good point to mention, thanks @CarterCall1 |
I also have the same problem. Do you have a solution to this problem? |
This error occurs even in version 6.5 |
I have tried to get to the bottom of this Behaviour, so i wrote this Test Action: And added the Following Test: The Test passes and the OpenApiParameter has the correct Description. |
I believe this is fixed in DotSwashbuckle, it has XML comment logic rewritten |
Duplicate of #2062 |
Hi!
I've updated Swashbuckle from 5.6.3 to 6.4.0 in my solution via the Swashbuckle.AspNetCore metapackage
There are some API method params with [FromForm] attribute
I can't see comments for those methods after the upgrade.
Rollback to 5.6.3 w\o changing anything else brings the comments back
The latest manual still suggests this should work (https://github.com/domaindrivendev/Swashbuckle.AspNetCore#include-descriptions-from-xml-comments)
Is there a bug?
#2308
I guess this issue is about the same situation.
I've decided to create another one and try to express the problem in a more clear way
https://stackoverflow.com/a/66378019/2498155
Here guys discuss the same IMO
The text was updated successfully, but these errors were encountered: