Enum as Required Field in ASP.NET Core WebAPI
Option 1: To use Custom RequiredEnum attribute and avoid JsonConverter attribute
Do not put JsonConverter on the AddressType enum. This StringToEnum is failing to map the string.Empty to enum value and it is throwing this error message.
Instead of that, you can write a custom required enum validator as shown below.
using System;
using System.ComponentModel.DataAnnotations;
public class RequiredEnumFieldAttribute: RequiredAttribute
{
public override bool IsValid(object value)
{
if (value == null)
{
return false;
}
var type = value.GetType();
return type.IsEnum && Enum.IsDefined(type, value);
}
}
Then you can use it like shown below:
public class AddressPostViewModel
{
[JsonProperty("addressType")]
[RequiredEnumField(ErrorMessage = "Address type is required.")]
public AddressType AddressType { get; set; }
}
Option 2: Use custom JsonConverter for AddressType
Add one custom CustomStringToEnumConverter which is derived from StringEnumConverter.
This method would throw an error if the value in JSON is empty.
public class CustomStringToEnumConverter : StringEnumConverter
{
public override object ReadJson(JsonReader reader, Type objectType, object existingValue, JsonSerializer serializer)
{
if (string.IsNullOrEmpty(reader.Value.ToString()))
throw new Exception("Address not provided");
return base.ReadJson(reader, objectType, existingValue, serializer);
}
}
Use this jsonConverter instead of default StringEnumConverter as shown below
[JsonConverter(typeof(CustomStringToEnumConverter))]
public enum AddressType
{
}
I've come-up with a solution that meets my requirements, although the code makes me cringe a little.
I kept the [Required]
attribute on the AddressType
property in the view model. The cringe-worthy part is that I had to make the property nullable
:
public class AddressPostViewModel
{
[JsonProperty("addressType")]
[Required(ErrorMessage = "Address type is required.")]
public AddressType? AddressType { get; set; }
}
On the AttributeType
enum itself, I replaced the StringEnumConverter
attribute with a custom JsonConverter
as suggested by @Manoj Choudhari:
[JsonConverter(typeof(CustomStringToEnumConverter))]
public enum AddressType
{
[EnumMember(Value = "Dropship")]
Dropship,
[EnumMember(Value = "Shipping")]
Shipping
}
This is the CustomStringToEnumConverter
:
public class CustomStringToEnumConverter : StringEnumConverter
{
public override object ReadJson(JsonReader reader, Type objectType, object existingValue, JsonSerializer serializer)
{
if (string.IsNullOrEmpty(reader.Value?.ToString()))
{
return null;
}
object parsedEnumValue;
var isValidEnumValue = Enum.TryParse(objectType.GenericTypeArguments[0], reader.Value.ToString(), true, out parsedEnumValue);
if (isValidEnumValue)
{
return parsedEnumValue;
}
else
{
return null;
}
}
}
The CustomStringToEnumConverter
can handle empty strings, nulls, and invalid strings. If it encounters an invalid enum value, it returns null
which is then caught when the required field validation (magic) occurs and the RequiredAttribute
error message is displayed in the JSON response.
While I don't like making the AttributeType
type nullable, the consumer of my API will see a consistent validation message if the AttributeType
value is wrong in the request JSON.
I don't think there is an out of the box data annotation validating enum values.
You can derive from the required attribute though:
using System;
using System.ComponentModel.DataAnnotations;
public class RequiredEnumAttribute : RequiredAttribute
{
public override bool IsValid(object value)
{
if (value == null) return false;
var type = value.GetType();
return type.IsEnum && Enum.IsDefined(type, value);
}
}
The Enum.IsDefined
method is checking if a given value
exists in the enum of given type
.
Usage:
[RequiredEnum(ErrorMessage = "Your error message.")]
public YourEnum EnumProperty { get; set; }
See this article.