open-feature
Enable nullables and enforce warnings as error
Description
Enable nullable reference types across the project to improve code safety, ensuring potential null-related issues are caught at compile time. Additionally, enforce strict compilation standards by treating warnings as errors, promoting code quality and adherence to best practices. This change aims to reduce runtime null reference exceptions and create a more robust codebase.
Hi @askpt To maintain consistency, should nullable enforcement and warnings-as-errors be enabled for test projects too, or is it preferred to apply these only to the source components?
Hi @askpt To maintain consistency, should nullable enforcement and warnings-as-errors be enabled for test projects too, or is it preferred to apply these only to the source components?
Yes. Enforce nullables in all flagd projects (tests and src)