Change Details

In T360445 a design is proposed to add support for adding and removing elements from arrays. This task is to make an initial implementation of that design and support this feature. {F54546674} **Design specification for nested fields**: Codex constructing forms [[ https://doc.wikimedia.org/codex/latest/style-guide/constructing-forms.html#conditional-and-nested-fields | docs ]] **Acceptance criteria** - [] Collection item fields are wrapped in a box, T364846 - [] Using multi-column fields to save vertical space and improve the double enumeration. - [] Add a trash button inside each module, clicking on it removes the element - [] Add a button to 'Add another (collection element)', clicking on it adds an empty item **Open questions** - Should all arrays have management? If not, how should an schema opt-in/opt-out from having management - Should we add support json-schema's `minItems`, `maxItems` vocabulary and let it configure the bahviour of the management (see [[ https://json-schema.org/draft/2020-12/draft-bhutton-json-schema-validation-00#rfc.section.6.4.1 | docs ]]) as part of this task?

In T360445 a design is proposed to add support for adding and removing elements from arrays. This task is to make an initial implementation of that design and support this feature. {F54546674} **Design specification for nested fields**: Codex constructing forms [[ https://doc.wikimedia.org/codex/latest/style-guide/constructing-forms.html#conditional-and-nested-fields | docs ]] **Acceptance criteria** - [x] Collection item fields are wrapped in a box, T364846 - [x] Using multi-column fields to save vertical space and improve the double enumeration. - [x] Add a trash button inside each module, clicking on it removes the element - [x] Add a button to 'Add another (collection element)', clicking on it adds an empty item **Open questions** - Should all arrays have management? If not, how should an schema opt-in/opt-out from having management - Should we add support json-schema's `minItems`, `maxItems` vocabulary and let it configure the bahviour of the management (see [[ https://json-schema.org/draft/2020-12/draft-bhutton-json-schema-validation-00#rfc.section.6.4.1 | docs ]]) as part of this task?

In T360445 a design is proposed to add support for adding and removing elements from arrays. This task is to make an initial implementation of that design and support this feature. {F54546674} **Design specification for nested fields**: Codex constructing forms [[ https://doc.wikimedia.org/codex/latest/style-guide/constructing-forms.html#conditional-and-nested-fields | docs ]] **Acceptance criteria** - [x] Collection item fields are wrapped in a box, T364846 - [x] Using multi-column fields to save vertical space and improve the double enumeration. - [x] Add a trash button inside each module, clicking on it removes the element - [x] Add a button to 'Add another (collection element)', clicking on it adds an empty item **Open questions** - Should all arrays have management? If not, how should an schema opt-in/opt-out from having management - Should we add support json-schema's `minItems`, `maxItems` vocabulary and let it configure the bahviour of the management (see [[ https://json-schema.org/draft/2020-12/draft-bhutton-json-schema-validation-00#rfc.section.6.4.1 | docs ]]) as part of this task?