Audit state of nullability support in ASP.NET Core

[captainsafia]

Filing this issue to investigate support for nullability across the stack. We did some work to enable nullability in public APIs in MVC/Blazor but there are still some scenarios we know need work, including:

• Update ASP.NET Core to use C# 8's nullable reference types #5680
• Templates aren't C# 8.0 nullability compliant by default #10921
• Field used in blazor component shown as "value assigned but never used" #20137
• Nullable annotations support #27389
• https://github.com/dotnet/aspnetcore/issues/24791

[ghost]

Thanks for contacting us.

We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.