New feature: if property is "Mandatory", the type is not nullable.

[fspezi]

I'm like your plugin.
But I suggest to add a feature to increase the power and utility.

If a Propety is "mandatory", the value must be declared. Then I expect that the type of property will be "int" or "datetime" or "bool". Instead of "Nullabile", "Nullable<DateTime" or "Nullable".

Are you right?

Thanks.

[JasonElkin]

Thanks @fspezi, I'm glad you like it.

The difficulty with the "mandatory" setting is that it doesn't guarantee that the value will not be null.

Content types are subject to change. Sometimes new mandatory properties are added to existing content, in those cases the existing content will have null values for those properties until that content is edited again. There's also the chance that someone has been doing something naughty with the content service such that content was saved without mandatory properties provided.

In Umbraco the value for any property could always be null 😬

The question then is what should we do if we encounter a null value for a mandatory property in the PropertyValueConveter? We could do what Umbraco's default converters do, and return the default value - but it will be the wrong value 🤔

Keeping the properties nullable at least makes sure that developers put their own logic for null handling in place and aren't just blindly accepting "0" or "01/01/0001 00:00:00" values from a property.

I guess we could always just throw an exception in those scenarios 🙈 - no that's a bad idea. But maybe something configurable? A way of registering some kind of default value resolver when unexpected nulls are encountered?