Form / foldkit-form

Limits

  • Headless: no view here (see foldkit-mixins-form), and no relation picker data. RelationOne and RelationMany carry the target Entity; listing its options is a query the application makes.
  • One Changed Message carries any draft, so a view can dispatch a draft of the wrong kind for a key. The form ignores it rather than storing it.
  • A key whose value is a struct is editable as a nested input of a relation's target, or through a control backed by a Bundle (Input.bundle). Rows keep the order they were added in; there is no reordering.
  • A control backed by a Bundle takes no check, its Bundle has no OutMessage and needs no services, and inside a nested form's rows it may have no Subscriptions or Resources.