A nice feature when using the templateform is that the required validators are automatically generated based on the data schema. It seems like Radzen does this based upon if the schema property is nullable or not?
This is the relevant snippet of my JSON data file (Swagger data source)
"ArticleValueParameter": {
"type": "object",
"properties": {
"articleCode": {
"type": "string",
"description": "Gets or sets the article code.",
"x-nullable": true,
"x-key": true
},
"validityEnd": {
"type": "string",
"description": "Gets or sets the last timestamp this carrier is valid, or null if still valid.",
"format": "date-time",
"x-nullable": true
},
"articleName": {
"type": "string",
"description": "Gets or sets the article name or description.",
"x-nullable": true
},
"volume": {
"type": "number",
"description": "Gets or sets the volume of the article packaging.",
"format": "double"
},
"nominalWeight": {
"type": "number",
"description": "Gets or sets the nominal weight for this article.",
"format": "double"
},
"nominalWeightDeviation": {
"type": "number",
"description": "Gets or sets the nominal weight deviation for this article.",
"format": "double"
},
"longevityDays": {
"type": "integer",
"description": "Gets or sets the number of days until expiry for this article.",
"format": "int32",
"x-nullable": true
},
"checksum": {
"type": "integer",
"description": "Gets or sets the checksum.",
"format": "int32"
},
"productId": {
"type": "integer",
"description": "Gets or sets the product id for this article.",
"format": "int32"
},
"carrierId": {
"type": "integer",
"description": "Gets or sets the carrier id for this article.",
"format": "int32"
},
"additiveId": {
"type": "integer",
"description": "Gets or sets the additive id for this product, or null if none.",
"format": "int32",
"x-nullable": true
},
"additivePercentage": {
"type": "number",
"description": "Gets or sets the additive percentage for this product, or 0 if no additive.",
"format": "double"
}
},
"additionalProperties": false,
"description": "Data transport object representation for defining an article."
}
Why are the properties Volume, NominalWeight, NominalWeightDeviation etc. generated as Nullable types when the JSON file does not specify them as nullable?
namespace EpmsFrontend.Models.EpmsDefinitions
{
public partial class ArticleValueParameter
{
[JsonPropertyName("articleCode")]
public string ArticleCode
{
get;
set;
}
[JsonPropertyName("validityEnd")]
public DateTime? ValidityEnd
{
get;
set;
}
[JsonPropertyName("articleName")]
public string ArticleName
{
get;
set;
}
[JsonPropertyName("volume")]
public double? Volume
{
get;
set;
}
[JsonPropertyName("nominalWeight")]
public double? NominalWeight
{
get;
set;
}
[JsonPropertyName("nominalWeightDeviation")]
public double? NominalWeightDeviation
{
get;
set;
}
[JsonPropertyName("longevityDays")]
public int? LongevityDays
{
get;
set;
}
[JsonPropertyName("checksum")]
public int? Checksum
{
get;
set;
}
[JsonPropertyName("productId")]
public int? ProductId
{
get;
set;
}
[JsonPropertyName("carrierId")]
public int? CarrierId
{
get;
set;
}
[JsonPropertyName("additiveId")]
public int? AdditiveId
{
get;
set;
}
[JsonPropertyName("additivePercentage")]
public double? AdditivePercentage
{
get;
set;
}
}