Suppose we're displaying an OpalForm<A>, its child forms <B>, and each B's target form <C>. For the creation of a new B and its C, if no data are filled out for B (leaving the defaults in place) but data are filled out for C, the new B and C were not being created.
This was hackily patched at some point (repository history has been lost), but the problem probably still occurs if instead it's OpalForm<A>, child forms <B>, each B's target <C>, and each C's target<D>, and we're not filling out B or C but are filling out D. Recursion is likely necessary in OpalFormUpdater.automaticChildren().
More details may be in the email thread entitled "Sufficient differentiators" from late December 2015.
Suppose we're displaying an
OpalForm<A>, its child forms<B>, and eachB's target form<C>. For the creation of a newBand itsC, if no data are filled out forB(leaving the defaults in place) but data are filled out forC, the newBandCwere not being created.This was hackily patched at some point (repository history has been lost), but the problem probably still occurs if instead it's
OpalForm<A>, child forms<B>, eachB's target<C>, and eachC's target<D>, and we're not filling outBorCbut are filling outD. Recursion is likely necessary inOpalFormUpdater.automaticChildren().More details may be in the email thread entitled "Sufficient differentiators" from late December 2015.