You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TL:DR;
add an "initialCount" property for listfields
Autoform has a great feature with handling array structures where
if there are minCount and maxCount defined on the schema
autoform displays minimum of minCount children ready to be filled and no [-] button
allows maximum of maxCount children and does not display [+] button after the last child
if there is an initialCount defined as a property of the [Array] field
displays initialCount children in the first render (if it is not less than minCount)
if the array is notoptional: true (meaning it should contain at least one child)
always displays at least one child
This allows for better UX design for forms with nested structures.
Uniforms does take into account minCount and maxCount but it lacks an "initialCount" feature.
Therefore, uniform's handling of such arrays of fields requires user interaction to be able to render the initial child input and users get confused about it when they don't see that first child input there and only a [+] button
The text was updated successfully, but these errors were encountered:
serkandurusoy
changed the title
[Feature request] Rendering of arrays (listfields)
[Feature request] Rendering an initial count of arrays (listfields)
May 29, 2016
TL:DR;
add an "initialCount" property for listfields
Autoform has a great feature with handling array structures where
minCount
andmaxCount
defined on the schemainitialCount
defined as a property of the [Array] fieldoptional: true
(meaning it should contain at least one child)This allows for better UX design for forms with nested structures.
Uniforms does take into account minCount and maxCount but it lacks an "initialCount" feature.
Therefore, uniform's handling of such arrays of fields requires user interaction to be able to render the initial child input and users get confused about it when they don't see that first child input there and only a [+] button
The text was updated successfully, but these errors were encountered: