You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the recent merge of the PR that centralized the management of nullable reference types in the main Directory.Build.Props file, we have ensured consistent default behavior across the entire repository. This change also included adding #nullable disable at the top of each .cs file, excluding files in projects where nullable reference types are already enabled.
To further clean up and simplify our codebase, we will gradually remove all #nullable disable directives from the src and test directories. This will avoid duplicate configurations and ensure consistency.
This change is part of our ongoing effort to improve code quality and maintainability. By centralizing the management of nullable reference types, we can ensure a more streamlined and consistent development experience.
The text was updated successfully, but these errors were encountered:
Describe the bug
With the recent merge of the PR that centralized the management of
nullable
reference types in the mainDirectory.Build.Props
file, we have ensured consistent default behavior across the entire repository. This change also included adding#nullable disable
at the top of each.cs
file, excluding files in projects where nullable reference types are already enabled.To further clean up and simplify our codebase, we will gradually remove all
#nullable disable
directives from thesrc
andtest
directories. This will avoid duplicate configurations and ensure consistency.This change is part of our ongoing effort to improve code quality and maintainability. By centralizing the management of nullable reference types, we can ensure a more streamlined and consistent development experience.
The text was updated successfully, but these errors were encountered: