Repository navigation
Implement C# 8.0 nullable standard #15
Description
from Sujay V. Sarma (@sujayvsarma) and copied from Azure-Samples/active-directory-aspnetcore-webapp-openidconnect-v2#249
Even if the project is not C# 8.0, consider implementing the nullable standard by suffixing ? to all parameters and returns that may be NULL.
This will be a breaking changing internal to the library & to consuming code. Therefore, consider publishing the changes only during a major cycle.
Activity
bgavrilMS commentedon Feb 18, 2020
That would be very cool indeed and the best time to do it is before releasing. Happy to help with this one, should not be too hard.
This blog describes the feature better https://devblogs.microsoft.com/dotnet/embracing-nullable-reference-types/
To quote from the blog:
Libraries can accurately describe the null behavior of the APIs, in a way that is checkable in client code at the call site. This raises expressiveness on API boundaries so that everyone can get a handle on the safe propagation and dereferencing of nulls. Nobody likes null reference exceptions or argument-null exceptions! This helps you write the code right the first time, and avoid the sources of those exceptions before you even compile and run the code.jennyf19 commentedon Jun 5, 2020
Bogdan Gavril (@bgavrilMS) or Peter (@pmaytak) can you put this in the correct milestone please? not a breaking change. thx
jmprieur commentedon Jun 10, 2020
Bogdan Gavril (@bgavrilMS) jennyf19 Peter (@pmaytak) henrikm (@henrik-me)
Talking with the ASP.NET Core team, ASP.NET Core 5 will support the nullable types.
BTW Barry mentioned the this is causing issues to ASP.NET Core : dotnet/aspnetcore#22656
jennyf19 commentedon Jul 13, 2020
Included in 0.2.0-preview release