Enable nullable reference types and refactor code#217
Merged
Conversation
This commit introduces nullable reference types across various files, enhancing code safety by explicitly indicating which properties can be null. Key changes include: - Updated `AspNetExtensions.cs` to use the null-forgiving operator `!` for method calls and property accesses. - Changed a private field in `AuthAgent.cs` from mutable to readonly to prevent modification after initialization. - Modified `WeatherForecastAgent` and `WeatherForecastAgentResponse` classes to use nullable types for properties. - Updated project files (`.csproj`) to enable nullable reference types. - Cleaned up `Program.cs` files by removing unnecessary using directives and ensuring configuration values are treated as non-nullable. - Minor refactoring for improved readability and maintainability, including the use of target-typed `new()` expressions. These changes collectively aim to improve code quality and maintainability.
tracyboehrer
approved these changes
Jul 19, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Our samples should be warning free. The AspNetExtensions.cs file will be copied to other projects, and VS uses nullable by default.
This PR fixes the nullable related warnings from the extension, and other places.
This commit introduces nullable reference types across various files, enhancing code safety by explicitly indicating which properties can be null. Key changes include:
AspNetExtensions.csto use the null-forgiving operator!for method calls and property accesses.AuthAgent.csfrom mutable to readonly to prevent modification after initialization.WeatherForecastAgentandWeatherForecastAgentResponseclasses to use nullable types for properties..csproj) to enable nullable reference types.Program.csfiles by removing unnecessary using directives and ensuring configuration values are treated as non-nullable.new()expressions.These changes collectively aim to improve code quality and maintainability.