I'm probably the best person to ask
-
-
Replying to @sgrif
cool :-); mostly trying to understand the aggregation cache...
1 reply 0 retweets 0 likes -
Replying to @cupakromer @sgrif
the “why" behind: 1) being private API, 2) only on persisted objs, 3) allowing the aggregate setters to still be used
5 replies 0 retweets 0 likes -
Replying to @cupakromer
Note: Overall the feature is poorly thought out and will likely be replaced with something more generic in the future
1 reply 0 retweets 0 likes -
-
Replying to @cupakromer
e.g. `user.address.street = "foo"` needs to work as well as `user.street_address = "foo"`
1 reply 0 retweets 0 likes -
Replying to @sgrif
`user.address` is frozen by Rails so the former likely would fail
2 replies 0 retweets 0 likes -
Replying to @cupakromer
Oh wow, I'd never noticed that before. Interesting
1 reply 0 retweets 0 likes -
Replying to @sgrif
yeah, i can sort of come up with a web work flow where that behavior _may_ be desired, but its def a little wonky, not very intuitive
1 reply 0 retweets 0 likes -
Replying to @cupakromer @sgrif
behavior of the aggregate value not updating; i do like the “freeze” (as it’s a “value” obj)
3 replies 0 retweets 0 likes
It's more possible to have that work now than it was when `composed_of` was written, but still tricky
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.