We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.
For technical issues or bugs please head to Support or our Developer Community. You can assign up to 20 votes in total. Thank you for your feedback.
Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.
With the nullable attribute features in .NET 5+, being able to know & account for if the given property is null, or if a validation method will indicate if a property is null, would be greatly beneficial for ensuring code written utilizing any EPiServer.* package is written cleanly & efficiently.
This would not break compatability with sites that choose to disable the nullable feature, as the attributes in question just indicate to the IDE what the acceptance & expectations are for properties being or having the capability of being null.
An example instance where adding nullability would aid in clarity are the ContentReference.IsNullorEmpty() method, where the property cannot be null when the method returns false. This would also help to clean up the various IDE warnings of properties being potentially null in different blocks of code, where the null check has already happened.