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
{{ message }}
This repository has been archived by the owner on Aug 27, 2019. It is now read-only.
Per the discussion in #9, there's a fundamental conflict that I'm not sure of how to best resolve, and that's about how to represent the form structure and style it properly. JSON Form has a notable limitation: form JSON cannot be nested (at least, not much). This makes it challenging to break the form up into its constituent sections while also providing decent granularity for each of the fields in that section. We have three choices:
Represent each form section in form.json as "type": "fieldset" groups. That eliminates any JSON Form display options (e.g., rendering select fields as radio buttons), and necessitates using CSS to group together fields...if that's possible.
Do not include form sections in form.json, but instead represent each field, one by one, serially. Use a combination of CSS and form.json options (e.g., prepend, htmlClass) to group fields together. Challenge: including descriptive text / titles before or after form groupings.
See if using a different JSON Schema library, e.g. Alpaca, will make it possible to nest form elements. Switching wouldn't be particularly difficult at this point, since JSON Schema is JSON Schema.
The text was updated successfully, but these errors were encountered:
There is a help data type, that allows arbitrary HTML to be injected between fields, but it's nested within two divs and a span. Useful, but not great.
Per the discussion in #9, there's a fundamental conflict that I'm not sure of how to best resolve, and that's about how to represent the form structure and style it properly. JSON Form has a notable limitation: form JSON cannot be nested (at least, not much). This makes it challenging to break the form up into its constituent sections while also providing decent granularity for each of the fields in that section. We have three choices:
form.json
as"type": "fieldset"
groups. That eliminates any JSON Form display options (e.g., rendering select fields as radio buttons), and necessitates using CSS to group together fields...if that's possible.form.json
, but instead represent each field, one by one, serially. Use a combination of CSS andform.json
options (e.g.,prepend
,htmlClass
) to group fields together. Challenge: including descriptive text / titles before or after form groupings.The text was updated successfully, but these errors were encountered: