Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 13:13

    solnic on v0.14.0

    (compare)

  • 13:10

    dry-bot on master

    [devtools] sync configs (compare)

  • 13:09

    solnic on master

    Bump dry-system to 0.14.0 (compare)

  • 13:08

    solnic on master

    Update changelog.yml (compare)

  • 10:31

    solnic on docsite-0.15

    (compare)

  • 10:31

    solnic on docsite-1.0

    (compare)

  • 10:17
    Travis dry-rb/dry-view (master) errored (706)
  • 10:14
    jchapron starred dry-rb/dry-types
  • 10:13

    dry-bot on master

    [devtools] sync configs (compare)

  • 10:13

    dry-bot on master

    [devtools] sync configs (compare)

  • 10:13

    dry-bot on master

    [devtools] sync configs (compare)

  • 10:13

    dry-bot on master

    [devtools] sync configs (compare)

  • 10:13

    dry-bot on master

    [devtools] sync configs (compare)

  • 10:13

    dry-bot on master

    [devtools] sync configs (compare)

  • 10:13

    dry-bot on master

    [devtools] sync configs (compare)

  • 10:13

    dry-bot on master

    [devtools] sync configs (compare)

  • 10:13

    dry-bot on master

    [devtools] sync configs (compare)

  • Jan 20 21:48
    Travis dry-rb/dry-view (master) errored (705)
  • Jan 20 21:44

    dry-bot on master

    [devtools] sync configs (compare)

  • Jan 20 21:44

    dry-bot on master

    [devtools] sync configs (compare)

Andy Holland
@AMHOL
Could use maybe/always but would probably be a bit weird
Piotr Solnica
@solnic
Then you can have things like "form_input.date"
Andy Holland
@AMHOL
:clap:
Piotr Solnica
@solnic
Hmm I like that yeah, so strict is just typecheck and coercible will first coerce then typecheck
Notice that type check can be anything not just class verification
Andy Holland
@AMHOL
Cool, so could just be a respond_to?
Piotr Solnica
@solnic
@AMHOL any constraint you want but I would prefer strict type check in most cases
Benjamin Klotz
@tak1n
optional_string haters gonna hate, but I love it :D
Piotr Solnica
@solnic
I am optional_string haters hater ;)
Benjamin Klotz
@tak1n
hehe :P
u are using kleisli under the hood right?
love unneeded questions xD
Piotr Solnica
@solnic
@tak1n yeah, I like kleisli
Benjamin Klotz
@tak1n
awesome :D
Piotr Solnica
@solnic
hey so maybe (no pun intended) we should switch to namespaced names?
Andy Holland
@AMHOL
+1
Piotr Solnica
@solnic
”strict.string” ”maybe.string” ”form_input.maybe.string”
Andy Holland
@AMHOL
here
Benjamin Klotz
@tak1n
+2
:D
Piotr Solnica
@solnic
holy moly I’m gonna love this lib (self-biased optimism)
Andy Holland
@AMHOL
:joy:
@solnic worth defining constants?
Piotr Solnica
@solnic
I don’t think we need constants
Andy Holland
@AMHOL
Dry::Data::STRICT_STRING = 'strict.string'.freeze
Dry::Hash.new(name: STRICT_STRING)
Piotr Solnica
@solnic
it’s gonna be more words to type
Benjamin Klotz
@tak1n
less string allocs
:D
Andy Holland
@AMHOL
That was my thinking
Benjamin Klotz
@tak1n
premature opt :D
Andy Holland
@AMHOL
lol
Piotr Solnica
@solnic
it’s gonna be better in mri 3.0 ;)
Andy Holland
@AMHOL
:laughing:
Piotr Solnica
@solnic
OPTIMIZE FOR THE UNKNOWN FUTURE ;)
Andy Holland
@AMHOL
mri 3.0 is gonna be Perl 6
Piotr Solnica
@solnic
luls
@AMHOL nice work on roda-flow, did you start using it in your project after all?
Andy Holland
@AMHOL
Yeah
Piotr Solnica
@solnic
cool man
Andy Holland
@AMHOL
It's working out nicely
Only a simple app though
Piotr Solnica
@solnic
Type.new(method(:constructor).to_proc.curry.(primitive), primitive) HATERS GONNA HATE ;)
Andy Holland
@AMHOL
lol
Benjamin Klotz
@tak1n
primitives, primitives everywhere
xD
@solnic I think I'll use dry validator for these use case specific validation rules I mentioned earlier
Piotr Solnica
@solnic
@tak1n not sure if @AMHOL released it already :)
Andy Holland
@AMHOL
I haven't