Nullable Property Value Converters for value types in Umbraco.
dotnet add package Our.Umbraco.Emptiness
If an editor hasn't set a value for a "value type" property, then these converters will return null instead of a default value. This makes editor intent clearer - you can tell the difference between an integer that an edtor intentionally chose to be "0" as opposed to an integer property that's been left empty.
Return null if an editor has not entered a value.
- NullableDatePickerConverter
- NullableDecimalConverter
- NullableIntegerConverter
- NullableLabelConverter
Though they don't have a null state in the UI, they can be empty if:
- A property has been added to a content type, but some content of that type has not been (re)published since.
- Content has been created via the API, without the property value having been set.
In these cases the following converters might be helpful...
Enabled by default. This converter returns the "Initial State" (default) value that has been configured in the property editor's settings.
Disabled by default.
You can configure Emptiness with appsettings.json like this:
"Emptiness": {
"EnabledConverters": [
"NullableDatePickerConverter",
"NullableDecimalConverter",
"NullableIntegerConverter"
],
"TrueFalseConverter": "DefaultValue"
}
This is the default configuration.
If provided, enables only the PVCs listed.
Property Value Converter names:
NullableDatePickerConverter
NullableDecimalConverter
NullableIntegerConverter
NullableLabelConverter
Determines the True/False (Yes/No) conveter to use for booleans.
Options:
Core
- use Umbraco's built in converter.DefaultValue
- use the YesNoDefaultConverterNullable
- use the NullableYesNoConverter
Copyright © 2022 Jason Elkin
Licensed under the MIT License.
Crate image created by vectorpocket - www.freepik.com