Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Opt-in Nullable Reference Types by default in templates
See original GitHub issueOpt-in Nullable Reference Types by default
Nullable Reference Types is a significant feature to decrease the possibility of bugs and it can improve robustness.
People who don’t follow the Microsoft DevBlogs even don’t know the existence of this feature, why not opt-in this feature in dotnet new template by default? If it was opted-in by default, new projects will consider the nullable issues, and in the future, most projects will not face the unexpected NullableReferenceException.
Solution
Make all existing templates in dotnet new opt-in Nullable Reference Types by default.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This was implemented in https://github.com/dotnet/templating/issues/3359, suggesting to close - let me know if you have any objections.
Thanks @vlada-shubina!