Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Apr 05 17:01
    emaraschio starred dry-rb/dry-monitor
  • Apr 04 15:38
    nepalez closed #74
  • Apr 04 15:38
    nepalez commented #74
  • Apr 04 10:40
    qortex commented #400
  • Apr 04 08:47
    flash-gordon closed #400
  • Apr 04 08:47
    flash-gordon commented #400
  • Apr 03 21:18
    qortex starred dry-rb/dry-types
  • Apr 03 21:14
    qortex edited #400
  • Apr 03 21:14
    qortex labeled #400
  • Apr 03 21:14
    qortex opened #400
  • Apr 03 19:18
    landongrindheim commented #74
  • Apr 02 19:47
    kamilski81 starred dry-rb/dry-monads
  • Apr 02 17:26
    waleedasif322 starred dry-rb/dry-types
  • Apr 02 14:59
    sskylar starred dry-rb/dry-monads
  • Apr 02 13:51
    kirin121 starred dry-rb/dry-container
  • Apr 02 10:56

    davydovanton on performance-improvements-for-rack-monitorring

    (compare)

  • Apr 02 10:55

    davydovanton on master

    Improve memory allocation for R… Merge pull request #34 from dry… (compare)

  • Apr 02 10:55
    davydovanton closed #34
  • Apr 02 02:25
    DaiAoki starred dry-rb/dry-types
  • Apr 01 14:39
    davydovanton commented #34
Andy Holland
@AMHOL
Yeah, I was more meaning say if you wanted a constraint on users#email and then another on credential#token for example
Piotr Solnica
@solnic
but a generic orm-agnostic/db-lib-agnostic predicate would be insane IMO
Andy Holland
@AMHOL
Ahh, cool
Yep, v.bad idea
Nice work BTW, looking awesome
Piotr Solnica
@solnic
@AMHOL thanks man, I’m close to cover all the use cases :)
but I’m gonna stop now, I feel confident enough that this is a good direction that more advanced stuff can be done later
Andy Holland
@AMHOL
Cool, I wish I could see a before and after on your million line validators lol
Piotr Solnica
@solnic
I gotta focus on rodakase and the book now
Andy Holland
@AMHOL
You written any of the book yet?
Piotr Solnica
@solnic
@AMHOL ain’t gonna happen, which is unfortunate, I’m leaving the project this month
Andy Holland
@AMHOL
Ahh, that's a shame
Piotr Solnica
@solnic
@AMHOL I’m about to start. first pages will be written on Friday
Andy Holland
@AMHOL
Nice :)
Piotr Solnica
@solnic
I need to come up with a rough plan first, but I have “intro” in my head so that’d be a start
I also need to figure out leanpub :)
90 stars on dry-validation btw :sparkles:
Andy Holland
@AMHOL
:D
Piotr Solnica
@solnic
it’s been a trending repo on github since last week, every day, I actually check it daily for whatever reason :joy:
Andy Holland
@AMHOL
lol to see if any of your repos are there ;)
Piotr Solnica
@solnic
that’s very likely
Andy Holland
@AMHOL
It is cool tho
Piotr Solnica
@solnic
morning
Hannes Nevalainen
@kwando
hola!
Piotr Solnica
@solnic
how would you call an object that is a result of running validation?
@AMHOL @timriley ^^ ???
hola @kwando :)
leaning towards Schema::Outcome
Hannes Nevalainen
@kwando
whats wrong with Schema::Result?
Piotr Solnica
@solnic
we have Validation::Result already
which is a result-per-rule
and we have Validation::Result::Set which is a result per rule-set
I actually need another concept, an array of result objects
no idea how to call it either
ok I know what to do
Tim Riley
@timriley
“Result” seems most natural, but since it’s already in use, “Outcome” isn’t too bad.
Piotr Solnica
@solnic
Validation::Result will become the enumerable containing Result::Value and Result::Set
Tim Riley
@timriley
“Product” is another possibility but it’s a term that’s already too loaded
Piotr Solnica
@solnic
question is, how to call abstract class for value and set lol
damn
it’s gonna be silly to have Schema::Result containing a…validation result
NAMING
;(
otoh it should be private
we want access to successes and failures
@timriley btw how does successes sound?
Tim Riley
@timriley
Sounds fine to me.
Piotr Solnica
@solnic
ok :)
Tim Riley
@timriley
It’s clear.
Piotr Solnica
@solnic
I’m about to break things /cc @timriley @kwando