Generic Task Form - Layout #1894
Description
The PR: #1678, by @mockoocy, introduced a really nice concept that made it possible to group the various inputs into sections. We had the occasion to try to put this to use the other day and we noticed a few things that would be nice to take a closer look at.
Ill try to make use of sub-issues for this issue, its a larger topic that in the end consists of a few smaller issues.
Documentation
First of all the documentation was actually quite hard to find, I knew that it was somewhere and we finally found it in the queue documentation, which also makes sense. But there is also this json -schema UI documentation. So one is easily a bit lost, it would be nice with a link or explaining section in the later.
Main Issues
- The first issue we had is a bug that crashes the front end if no
{group: }attribute is specified for a field that has other"ui:configuration. (Ui crashes if no {group: } attribute is specified for a field that has other"ui:"configuration. #1895)
Improvement on layout
- We think that the layout and UX can be improved by adding the unit right after the label instead of in the information circle (Render checkboxes on one line (without label duplication) #1896)
- Render checkboxes one line (without duplicating its label) (or all components with their labels on one line) (Rendring of unit (short-description) #1897)
- Default for show-more (Defaullt to show-more #1898)
- Readonly fields are not displayed the same #1899