Mitch VanDuyn comments

Results 234 comments of


                                            Mitch VanDuyn

add `#html_attr_name` method

are the conventions used by any code? As in would I ever "have" to use the convention, or is it just simply a convention to keep things tidy. In which...

in edge branch, the limit scope doesn't work unless you explicitly regulate it

not sure but I think this might be because scope :limit, ->() {} scope :offset, ->() {} is in the CLIENT side base class. this means the client will assume...

do_not_synchronize isn't inherited

its because the internal instance data is not being inherited correctly

do_not_synchronize isn't inherited

probably need a way to turn it on and off then i.e. turn it off in ApplicationRecord, but then turn it back in specific modules.

Errors aren't cleared if you don't save because a record hasn't "changed"

Good catch

changing record attributes is causing too many renders

@mareczek - linked_copies could be problematic. I would hope to implement .2 such that once objects are no longer referenced they can be garbage collected. The `linked_copies` method would prevent...

changing record attributes is causing too many renders

Well sure, but why? Perhaps we can figure out a more built-in solution if we know what the purpose is

changing record attributes is causing too many renders

so in that case you actually would want to start at the last copy, and move backwards right? But I would hate to see the functionality overloaded for this purpose....

changing record attributes is causing too many renders

So here is a proposal... but I am going to follow it with something completely different :-) We add an `avatar` capability to AR models on the client. An `avatar`...

changing record attributes is causing too many renders

So instead of all this, how about using a just using a decorator. (see https://github.com/drapergem/draper as well) Avatar[some_record] returns a nice new Avatar of some_record. The end. This whole thing...