Nick Sutterer

I have a cool idea. So my main idea was to push people towards using their model wrappers manually, and Reform shouldn't know anything about how the internals of your...

No, it does not. The twin can be a `Composition` or whatever you want, we just have to provide a way to specify how it's instantiated, then you can use...

I am thinking about providing that in all other gems, too, `Operation`, Cells, and Representable.

Thanks @tilod, valid comments! 1. You can copy properties from whatever to your twin and vice-versa automatically. No need to have redundancy. 2. `#sync` is not meant to be overridden,...

Reform is absolutely _not_ designed to work straight on models, @contentfree. The `Composition` feature in turn has nothing to do with associations, what makes you think so? It's designed to...

@contentfree Your snippets do look perfectly fine to me. After having a look at it, I strongly advice you to use Trailblazer, though, as your controller code is the perfect...

I don't mind one before- and after accessor in Disposable, but this is absolutely not code for a form, but must go to the update operation wrapping this.

@fran-worley We can put this into Disposable into the `Twin::Changed` module, this should be fine there. Or you think it's wrong? Agreeing that this ain't no stinky Reform thing, though!

Hi @HoneyryderChuck - this is missing. The underlying parser, the _Representable_ gem, doesn't support this out-of-the-box. You could probably do that manually in a "virtual" populator, since it receives the...

The populator is **not** called for a `nil` fragment... that is indeed unexpected behavior.....