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
The current implementation simply swaps out the collection. But what if the collection is virtual? We'd like to capture requests in the memento to add or remove and then play them on the object when the form is saved.
Currently, when a cached memento is committed, the work is done here:
Object>>write: anObject using: aDescription
"This hook is needed so that e.g. mementos and adaptive models can implement their own behavior. All other entry points e.g. MADescription>>#read: should come through here"
aDescription accessor write: anObject to:self
This won't work for this to-many proposal, which would have to delegate back to the description. MADescription already has an analogous method:
write: anObject to: aModel
^ aModel write: anObject using:self
The text was updated successfully, but these errors were encountered:
The current implementation simply swaps out the collection. But what if the collection is virtual? We'd like to capture requests in the memento to add or remove and then play them on the object when the form is saved.
Currently, when a cached memento is committed, the work is done here:
This won't work for this to-many proposal, which would have to delegate back to the description. MADescription already has an analogous method:
The text was updated successfully, but these errors were encountered: