Nick Sutterer
Nick Sutterer
Actually, I believe that Disposable only calls the setter if the value has changed, but I might be wrong. In your case, whatsoever, the problem seems to be the `collection`...
Or, wait a minute, did you say that `model.file = model.file` also breaks?
@akz92 Could you try this? https://github.com/apotonick/disposable/blob/master/lib/disposable/twin/sync.rb#L133 This module included in the `FileForm` will prevent `#sync!` from writing if the property hasn't changed.
Hm, that sounds like unintended behavior (a "bug"). Can you check disposable's tests if we cover collections where only one property is changed in combo with `SkipUnchanged`?
Cool idea!!! :heart: I'll try to get it into 1.1.1?
Allow dynamic `collection :sources do ... end `s where each source item can have different `property`s depending on the underlying item model. Allow that also for the incoming input hash.
That's basically the idea of the underlying twin. Reform was written to decouple your models from forms, so you don't need to expose your table structure via forms. Many use...
Awesome!!! :heart_eyes: Twins were designed to work with classic DB "models". They 1. read property values from the model(s) as per defined schema 2. then expose accessors, e.g. `twin.email =...
Give me some examples of what you want and I'll tell you how to do it, how does that sound?
Cool example, @JakeBecker!