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
Field dependencies e.g. for web forms. For example, I have an online compounding interest calculator. If one field is changed, another should autoupdate. For more info, see Field Dependencies #152.
Checked mementos. Right now there are dumb dictionaries. The problem is when the model is more complex than "one change affects one field".
Use case: I have a "Federal Register" work representing the series. Now, I have a particular issue "Vol. 87, No. 18/Thursday, January 27, 2022" that I want to add as a child. Currently, the to-many relations just copy the collection and add a new item, but in this case, the parent implements #addChild: because there is mutual setup to be done between the parent and the child. I don't see how this can be handled with the current API. There is the initialization block, but this setup should only be done if the child is actually added, not on child creation.
The text was updated successfully, but these errors were encountered:
To limit bug bankruptcy (see https://www.joelonsoftware.com/2012/07/09/software-inventory/) this issue has been automatically marked as stale because it has not had any activity in 6 months. If no further activity occurs, it might be closed. If this issue remains important to you, please comment to reactivate the issue. Thank you for your contributions.
stalebot
added
the
stale
Closed after 6 months to limit bug bankruptcy; can be reopened if still important
label
Nov 22, 2022
Two use cases jump out:
Use case: I have a "Federal Register" work representing the series. Now, I have a particular issue "Vol. 87, No. 18/Thursday, January 27, 2022" that I want to add as a child. Currently, the to-many relations just copy the collection and add a new item, but in this case, the parent implements
#addChild:
because there is mutual setup to be done between the parent and the child. I don't see how this can be handled with the current API. There is the initialization block, but this setup should only be done if the child is actually added, not on child creation.The text was updated successfully, but these errors were encountered: