Honestly, that was added so long ago its hard to say what the original rationale was ![]()
- Ash strings (by default), cast to
nil. - We have the
nil_items?constraint, which rejects nil values. For usempty_valuesis a separate kind of thing, representing when the entire list is empty. - I think what you want is a new constraint, called
remove_nil_items?that will remove nil items instead of making them an error if they exist.






















