Mitch VanDuyn

probably can use this gem: https://github.com/pvande/differ basic strategy would be to send a checksum as "current value" and checksum + diff as new value. if checksums before update match then...

probably means complete refactor of has_many_through. What has_many_through should probably be doing is something like this: Consider `TodoItems.has_many :commenters, class: User, through: :comments` `todo_item.commenters.first` => `todo_item.comments.first.user` In other words it...

There are three remaining areas that will speed up fetches server side 1) when the client requests a fetch it feeds all currently changed records that have not yet been...

The following will introduce a big breaking change to the semantics of composed_of (aggregations) on the client side. ```ruby # assume address is a composed of object in User some_user.address...

stopped working when we added scheme type checking

so that you can say `ReactiveRecord::Base.system_reset!` to reinitialize all the reactive-record data structures (without doing a full Application::Boot which would reset the UI)

AR lets you do this: `scope :foo -> () { self }` but hypermesh expects scopes to always return relationships you can effectively get this result by doing `scope :foo,...

add `#html_attr_name` method

3

just a handy helper to add the ActiveRecordBase (on the client) (it would jus be added to InstanceMethods module) ```ruby def html_attr_name(attr) "#{model_name}#{to_key}-#{attr}" end ``` See https://github.com/ruby-hyperloop/hyper-react/issues/244 for details on...

add `ReactiveRecord.on_fetch_error` call back method

6

so that for debug, logging, etc purposes you can define it yourself. ```ruby module ReactiveRecord def self.on_fetch_error(e, params) # do whatever you need to end end ```

after that see test case in batch3/edge_cases.rb (line 54 approx)