Francis George

I'm also seeing this and it's pretty jarring. The remote_method does seem to work, there's just that warning. If I make foo= a server method then it stops working. Likewise...

I'm using a server method like an attribute in order to do some additional processing on a field but still have Hyper Mesh automatically update the frontend. This is what...

@catmando Yeah it is just to get rid of the error. Without suppressing the warning a million lines of base64 image data get printed to the browser console and Chrome...

This seems less useful than `to_key` unless `for` and `name` params do some magic, which I think they probably shouldn't. As there's no obvious "right" way of naming for/name in...

See https://github.com/ruby-hyperloop/hyper-react/issues/245 for how I use this in a smart form input component. Simply some human readable and useful yet unique identifier to link `name` and `from`

1st issue we found is **unique constraints**: If you have a join table you may well have a compound unique constraint on it as we do below. For data integrity...

I have started selectively putting `do_not_synchronise` in models that don't need to update live, to reduce broadcast traffic. It works fine like that. Before I was trying to use it...

Na I agree not adding anything big and new for 1.0, mainly refining.

Well I came to the conclusion that it's not easy to get saving of HABTM working. Because it translates to has_many :through which Hyperloop doesn't support saving to. But even...

Not sure I'm following 100% but being able to get an array of IDs is basically the same as getting a count. I think I've seen Hyperloop return a bunch...