Closed hazzik closed 5 years ago
@maca88 added the bug label
Not a bug per se.
Also, this, probably, needs to be controlled by an option, because on older compilers this directive could throw error on build.
Not a bug per se.
Changed to enhancement.
this, probably, needs to be controlled by an option
Nullable
tag in csproj. The mentioned PR does not work when using .NET 4.6.1 as the API for checking nullables is not available.
The
<auto-generated>
resets the#nullable
flag (disables it), so the generator should emit#nullable restore
at the top of the generated file (after the/// <auto-generated>
) to restore the flag to project's default settings. Otherwise the code could become not compilable.