Mitch VanDuyn

of course :-) thanks!

Agree. For clarity my understanding is that 3 uses 2, and for example you could have reactrb-sinatra that would also use 2. And how about reactrb-testutils or some such? (or...

lets keep the testutils on a separate issue then...

Further thinking about this... why not just accumulate the active_record previous_changes values until the the transaction is exited? Understand both these suggestions would probably require monkey patching, but still it...

It seems that this fix is working (see notes below) ```ruby module ReactiveRecord class Broadcast def self.after_commit(operation, model) # Calling public_columns_hash once insures all policies are loaded # before the...

So the reason that this was changed to submit the entire record, is that when making multiple saves within an active-record transaction, only the last values saved by previous_changes will...

is that a working example or what? I have the same question... did you find a better answer?

This is worse than I thought. Take `param :read_only` for example. It doesn't work because read_only gets automatically translated to readOnly. This is done because react.js maps `readOnly` back to...

From our code base. This is the actual example that trigged this issue ``` ruby def render div do button(params.attributes.merge({id: "#{job.finishing.id}_trigger_button"})) do # fixing this would allow us to write:...

I would request that we keep the syntax consistent with params and state: params.foo state.foo context.foo Also I am not clear on what the type is for, does it have...