[dasc] Arrays support min/max

[auniverseaway]

As an author, I would like to know if I am under or over an array's min / max values.

Criteria of acceptance

1. Uses existing validation tools to flag if over or under.
2. Does not prevent or force a min / max as the author should be able to over / under shoot to better organize WIP.

Additional context

At first I thought we would want to enforce this, but I think its better to let an author work with the validation signals to get into compliance. If you think about an author that has 4 items, needs to shuffle data around, but cannot add a 5th until they remove another. The same is somewhat true of mins. I think we would end up getting a lot of empty items rather than correct data.

[kozmaadrian]

At first I thought we would want to enforce this, but I think its better to let an author work with the validation signals to get into compliance. If you think about an author that has 4 items, needs to shuffle data around, but cannot add a 5th until they remove another. The same is somewhat true of mins. I think we would end up getting a lot of empty items rather than correct data.

I’m not fully convinced that’s the right approach. The JSON schema is the single source of truth, not only for structure, but also for validation. If the schema specifies that there must be four items, the UI must prevent adding a fifth. Likewise, if a field’s maximum value is defined as 10, the UI should not allow values above 10.

Introducing custom rules creates ambiguity. It requires learning and maintaining additional logic outside the schema, which undermines the principle of having a single source of truth.

Furthermore, adding internal validation rules would conflict with the JSON validation library, which validates data strictly against the schema and nothing else.