Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
Benjamin Klotz
@tak1n
irb(main):009:0> Date.new("".to_i)
=> #<Date: 0000-01-01 ((1721058j,0s,0n),+0s,2299161j)>
irb(main):010:0> Date.new("")
ArgumentError: comparison of String with 0 failed
        from (irb):10:in `<'
        from (irb):10:in `new'
        from (irb):10
        from /usr/bin/irb:11:in `<main>'
why ruby why..
Piotr Solnica
@solnic
@tak1n there’s a lot of gotchas, that’s why isolating them is so important
Benjamin Klotz
@tak1n
true
Piotr Solnica
@solnic
update: dry-data runs on production :D
Benjamin Klotz
@tak1n
:clap:
Luca Guidi
@jodosha
@solnic bump to 1.0 then :D
Piotr Solnica
@solnic
haha, no. ;)
still a lot to do
Hannes Nevalainen
@kwando
joho, congratz! =)
Piotr Solnica
@solnic
I gotta figure out a way to provide my own container for types now that I could control
because of BS code reloading in rails, mostly (but comes with more benefits too)
Hannes Nevalainen
@kwando
+1 for that
I had rails reloading issues with the released version =/
Piotr Solnica
@solnic
yeah it’s broken :D
reminder: 0.0.1
Hannes Nevalainen
@kwando
I know, I know =)
Piotr Solnica
@solnic
predicates are the next step btw, then i’ll add form_input category with different coercion rules and mechanics, then finally dry-validator could leverage that
and THEN I’ll ditch AM in rom-model for validators
then it’ll be a great moment to put together rodakase and start writing my book, ugh, so much work
Andy Holland
@AMHOL
@nepalez @solnic I guess I missed that use-case because I created it with the intention on IoC in which case you wouldn't want duplicates, but there is a much larger array of use-cases popping up now so it's worth exploring I think
Sorry, I know that was a long time ago when it was mentioned (the transproc style importing)
Andrew Kozin
@nepalez
@AMHOL NP. When I pull myself out of rom-migrator, I'm going to return to that thing
Andy Holland
@AMHOL
Cool, i haven't had a chance to look at rom-migrator in a while but looked good last time
You mean Transproc BTW? Let me know, we might be able to change dry-container to fit, do you want commit access for dry?
Sorry about the broken English, walking and typing on my phone lol
Andrew Kozin
@nepalez
@AMHOL I meant returning to that feature in dry-container and sending a PR :)
IMO, the only thing that should be done in transproc by itself is a removal of deprecated staff. Maybe(splitting it to core and libs). But all of this can wait.
(The English is broken? OMG! :fearful: )
Andy Holland
@AMHOL
I edited it when I got home lol
Benjamin Klotz
@tak1n
anybody going to euruko? :)
Andy Holland
@AMHOL
Nope but looks good
I want a Ruby conference in Manchester lol
Andy Holland
@AMHOL
@solnic you cool with this? https://github.com/dryrb/dry-dependencies
Piotr Solnica
@solnic
@AMHOL this can be useful for cases where you don’t want to use auto-inject, there is a gem that does exactly that called concord but it is super opinionated and uses a limit of 3 collaborators
btw I wanted to tweak auto-inject to define a constructor with hash as arg (or k/v args maybe)
this way it’s easier to instantiate an object and pass a mock
Andy Holland
@AMHOL
Yeah, sounds good, could use dry-dependencies to define the constructor in auto-inject too
Piotr Solnica
@solnic
yes, that’s a good idea, I thought about this too
@AMHOL ^
Andy Holland
@AMHOL
:)
Piotr Solnica
@solnic
but maybe let’s call it dry-constructor or dry-initialize?
one more thing - I’d like to fork equalizer into dry-equalizer and tweak it a little bit; seems like Dan hasn’t got the time to maintain it and equalizer is heavily used by lots of projects so it’s harder to make changes in it
there’s a weird behavior in equalizer right now where it tries to do Object#coerce which was a design mistake, it goes back to the roots of this library which is axiom gem where this behavior was useful, but as a generalized interface it’s actually causing issues (and makes it slower too)
object equality is pretty fundamental in our style of coding, so I think dry-equalizer would be an awesome addition
Andy Holland
@AMHOL
Yeah, definitely, assuming Dan is OK with that
Could go with either of those, went with dry-dependencies as it adds the dependencies macro
Piotr Solnica
@solnic
@AMHOL I prefer module subclassing, it removes the need for defining new class methods
Andy Holland
@AMHOL
With the dry-dependencies thing?
Piotr Solnica
@solnic
yes