-
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
[BUG] Missing OpenAPI spec nullable in classes with refs #2225
Comments
About ValueTuple support: [ProducesResponseType(StatusCodes.Status200OK, Type = typeof((User? userData, UserGroupLink? userGroupLinkData)))] produce: "UserUserGroupLinkValueTuple": {
"type": "object",
"additionalProperties": false
}, in |
This one blocks us from using swashbuckle. |
Up |
Same issue with nullable properties. How to force #ref to be nullable in code?
ver 6.5.0 generates
|
Is there any movement on this?
It can be handled better using |
To make issue tracking a bit less overwhelming for the new maintainers (see #2778), I've created a new tracking issue to roll-up various nullability issues here: #2793. We'll refer back to this issue from there and include it as part of resolving that issue, but I'm going to close this one to help prune the backlog. |
I have generated code:
It produces this json open API spec for
UserService_AddNewUserToAccountControllerOutput
:It should produce this json open API spec:
Versions:
Also, you might want to add support for ValueTuple. I was not able to use it directly, so I generate an additional class with an explicit operator like here. I tested this on version 6.1.4
The text was updated successfully, but these errors were encountered: