Arrays

[mohsen1]

Arrays are the most challenging aspect of this component.

Here are the questions regarding arrays:

• How we provide add/remove functionality for array items?
• Should we provide re-ordering functionality?
• How we allow custom templates do clever things with arrays? Things like using tabs for each array element

[bvaughn]

This kind of overlaps with #10. We should probably discuss collections in one place (here? there?) only to avoid confusion.

[mchapman]

I see a distinction (both in visual and data representation) between arrays of strings and arrays of objects.

Add / remove there are more options with string arrays.

Auto add - from here

Explicit add

With objects I don't think I have seen an alternative to explicit add (from here:

Re-ordering
Think this should be optional - it is quite heavy and not much use in some scenarios.

** Clever things **
Maybe premature to address this?

@bvaughn I appear to have continued here. I had already started capturing screen shots when I saw your post,

[bvaughn]

There's a side-effect of implementing either of the add-methods above in forms-js though: it requires users to fully describe their data with validations. (We can't initialize an object unless we know all of its possible attributes.)

There's also a further-down-the-chain side effect, which is to say that.. it complicates our templating system. Unless we insist on auto-generating all of the form markup- something I am pretty strongly apposed to (but something we should discuss on another ticket, perhaps)- then implementing our own collections-management (like you've screenshot) would take away a users ability to customize the presentation of fields within a child object.