-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Validate default Razor and Blazor project templates with nullability enforcement enabled doesn't result in unexpected warnings. #13072
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
Comments
@danroth27 there are several locations in our Blazor project templates that aren't nullable enforcement friendly. Is this something we want to address or leave as is? I'm uncertain of C#'s plans to turn the feature on by default or not so this decision might be largely based on that decision as well. For context in Blazor server side app there's:
Blazor WASM:
|
@NTaylorMullen We should address these, so go ahead and file an issue if you haven't already. |
Looks like I already filed an issue for this a while back that's in 3.1.0. Feel free to move the milestone if you want: #10921 |
The text was updated successfully, but these errors were encountered: