ASP.NET Web API: Array vs. List

Asked Aug 19 '16 at 10:51

Active Aug 19 '16 at 10:51

Viewed 108 times

I had a property LineItems which was of type List<LineItem>, it was [Required]. We realized that it was possible to send an empty array via JSON ("lineItems": []) which was not what we wanted to achieve with the [Required] attribute.

I've thought about a solution, maybe a custom filter but then I found out that it is possible to use [MinLength(1)]. Unfortunately only in the case of an array (LineItem[]).

My Question now is: Are there any arguments to favor one type over the other regarding the interface?

asked Aug 19 '16 at 10:51

timmkrause

3,367
4
32
59

Look at http://stackoverflow.com/a/5146766/4275342 – Roman Marusyk Aug 19 '16 at 10:55
Thanks, found that already. But I think I would favor the built in solution if there is no downside for an array. – timmkrause Aug 19 '16 at 11:03
I don't think there is some in built one that you can use right out of the box. Going for a custom attribute for yourself would be probably better. :) – Swagata Prateek Aug 19 '16 at 14:34

ASP.NET Web API: Array vs. List

0 Answers0