@sgrif @tenderlove I get it. I just think we need to call it out more specifically, because I blew hours on it, and I know AR internals.
-
-
Replying to @erniemiller
@erniemiller@tenderlove Definitely should call it out in the 4.2 docs, though. Wanna open a PR?1 reply 0 retweets 0 likes -
Replying to @sgrif
@sgrif@tenderlove Yeah, plan to — gimme a few — catching up on some stuff over here.2 replies 0 retweets 0 likes -
Replying to @erniemiller
@sgrif One problem: can't find any solid docs yet on minimal API for a Type object. Not keen on recommending users subclass Type::Value1 reply 0 retweets 0 likes -
Replying to @erniemiller
@sgrif …if only because it has precision/scale/limit and possibly other stuff that's not relevant for a domain object attribute1 reply 0 retweets 0 likes -
Replying to @erniemiller
@sgrif It looks like it might just be cast/serialize/deserialize?2 replies 0 retweets 0 likes -
Replying to @erniemiller
@sgrif Meh, scratch that. More involved than that. Suggestion: configuration of precision/scale/limit should be in a Numeric Value subclass3 replies 0 retweets 0 likes -
Replying to @erniemiller
@erniemiller Strings, dates, and more also use those. The issue is avoiding `respond_to?` if it's used outside of the class.1 reply 0 retweets 0 likes -
Replying to @erniemiller
@sgrif Sometimes it's better to even duplicate the code (remember it's not about duplicated code, but duplicated domain logic)2 replies 0 retweets 0 likes
@erniemiller Yeah, I agree. They weren't put on Value as an explicit decision, just kinda stuck around.
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.