Support for Nullable Reference Types

[Compusa]

Are there any plans to add support for Nullable Reference Types? It would be nice, and with NRT we would no longer need to annotate required properties with the [Required] attribute.

[alesdvorakcz]

I am also looking for a way how to set all non-nullable properties in schemas required by default. Is there any other way except manually adding Required attribute everywhere?

[esbenbach]

Creating a pull request ;)

[felschr]

@alesdvorakcz
I agree, it would be nice if Swashbuckle behaves the same as the ASP.NET Core validation system:

The validation system in .NET Core 3.0 and later treats non-nullable parameters or bound properties as if they had a [Required] attribute.

— https://docs.microsoft.com/en-us/aspnet/core/mvc/models/validation?view=aspnetcore-3.1#required-attribute

[Lonli-Lokli]

Waiting for the same. With Nullable feature enabled it's still required to add Required attribute.

[esbenbach]

@domaindrivendev I would be willing to give it a try if you think you would accept a PR for it.
Presumably there would be a need to "opt-out" like there is with the validation in aspnetcore.

Also, i expect the Nullable type detection would more or less be equivalent to what is done in the asp.net core repo:
https://github.com/dotnet/aspnetcore/blob/0517745c08d1bc85009f1ca41a41d77176eeea60/src/Mvc/Mvc.DataAnnotations/src/DataAnnotationsMetadataProvider.cs#L357

Which is not exactly pretty - but I doubt I can come up with something better.
Would that approach be acceptable?

[domaindrivendev]

@esbenbach - sounds reasonable. I'll keep an eye out for your PR and will try my best to provide prompt feedback

[eluchsinger]

Any news here?

[esbenbach]

Unfortunately no - due to Covid19, lots of stuff has prevented me from looking into this, and the timeframe is pretty grim. Someone else should feel free to give it a try :)