dry-rb/chat

WE MOVED TO ZULIP => https://dry-rb.zulipchat.com <=

Piotr Solnica

@solnic

@jdickey we're switching to Zulip

Jeff Dickey

@jdickey

Understoon

Piotr Solnica

@solnic

we also tried Slack, Rocket, Discord and Spectrum

eventually it turned out Zulip is the best option

Piotr Solnica

@solnic

@/all hey, after 2 weeks of testing we decided to switch to Zulip and we are saying "good bye" to Gitter. From April 1st (no kidding) we'll be hanging out in Zulip and stop paying attention to this Gitter chat. You can join our Zulip organization here: https://dry-rb.zulipchat.com/register/

ps. rom-rb gitter chat will move too

Philip Arndt

@parndt

:tada:

Brice Sanchez

@bricesanchez

:tada:

Orban Botond

@orbanbotond

Hi Guys,

How can I use succesfully the inheritance in dry-rb transactions?

Here is the code which shows that it just doens’t work:

require 'spec_helper'

module CRUD
  class Update
    include Dry::Transaction

    step :validate
    step :persist


    def validate(input)
      Success(input.to_s + model_class.to_s)
    end

    def persist(input)
      Success(input.to_s + model_class.to_s)
    end
  end

  class ORMModel1
  end

  class Update1 < Update
    def model_class
      ORMModel1
    end
  end
end

describe 'ParamOverride' do
  context 'update1' do
    subject { CRUD::Update1.new.call params }
    let(:params) { {a:1,b:2} }

    context 'negative cases' do
      specify 'inheritance just does not work' do
        expect(subject).to be_success
        expect(subject.value!).to_not eq('{}ORMModel1')
      end
    end
  end
end

Viet (Drake) Tran

@tiev

What is the output? Btw, can you move to zulipchat? This gitter is abandoned

Orban Botond

@orbanbotond

@tiev I expected the output to be '{}ORMModel1’

Viet (Drake) Tran

@tiev

And I guess the actual output is '{:a=>1, :b=>2}ORMModel1ORMModel1'

Orban Botond

@orbanbotond

@tiev no, the actual output is {:a=>1, :b=>2}

Lairan

@alex-lairan

ps. rom-rb gitter chat will move too

Sergey Kukunin

@Kukunin

Hi guys. I want to serialize/deserialize my dry-struct to JSON. Is there a way to derive a new dry-struct which can build an original from JSON? I expect it to convert all types to their JSON equivalents

I expect it to work recursively

Lairan

@alex-lairan

Please, read my last message :)

Martín Fernández

@bilby91

Hello! I’m looking into dry-validations 1.X and I was wondering if there is any way to compose multiple contracts, basically delegate the validation of a given property from within a contract to another contract.

Tonni Tølbøll Lund Aagesen

@ta

2.5.3p105> require "dry-types"
=> true
2.5.3p105> include Dry.Types()
=> Object
2.5.3p105> Params::Integer["1"]
=> 1
2.5.3p105> Params::Integer[1]
=> 1
2.5.3p105> Params::Time["2019-11-26 15:50:12 +0000"]
=> 2019-11-26 15:50:12 +0000
2.5.3p105> Params::Time[Time.new]
Traceback (most recent call last):
       16: from /var/lib/gems/2.5.0/gems/bundler-1.15.4/lib/bundler/cli.rb:13:in `start'
       15: from /var/lib/gems/2.5.0/gems/bundler-1.15.4/lib/bundler/vendor/thor/lib/thor/base.rb:466:in `start'
       14: from /var/lib/gems/2.5.0/gems/bundler-1.15.4/lib/bundler/cli.rb:22:in `dispatch'
       13: from /var/lib/gems/2.5.0/gems/bundler-1.15.4/lib/bundler/vendor/thor/lib/thor.rb:387:in `dispatch'
       12: from /var/lib/gems/2.5.0/gems/bundler-1.15.4/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
       11: from /var/lib/gems/2.5.0/gems/bundler-1.15.4/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
       10: from /var/lib/gems/2.5.0/gems/bundler-1.15.4/lib/bundler/cli.rb:362:in `exec'
        9: from /var/lib/gems/2.5.0/gems/bundler-1.15.4/lib/bundler/cli/exec.rb:27:in `run'
        8: from /var/lib/gems/2.5.0/gems/bundler-1.15.4/lib/bundler/cli/exec.rb:74:in `kernel_load'
        7: from /var/lib/gems/2.5.0/gems/bundler-1.15.4/lib/bundler/cli/exec.rb:74:in `load'
        6: from /usr/bin/irb:11:in `<top (required)>'
        5: from (irb):6
        4: from /var/bundler/gems/dry-types-1.2.1/lib/dry/types/type.rb:49:in `call'
        3: from /var/bundler/gems/dry-types-1.2.1/lib/dry/types/constructor.rb:59:in `call_unsafe'
        2: from /var/bundler/gems/dry-types-1.2.1/lib/dry/types/constructor/function.rb:61:in `call'
        1: from /var/bundler/gems/dry-types-1.2.1/lib/dry/types/coercions.rb:87:in `to_time'
Dry::Types::CoercionError (2019-11-26 16:16:50 +0000 is not a string)

Is it on purpose that Param::Time[] no longer accepts a Time object?

I would expect coerce to do something like obj.class == Time ? obj : coerce(obj, Time)

Tonni Tølbøll Lund Aagesen

@ta

This was also the case in previous versions, I believe

Tonni Tølbøll Lund Aagesen

@ta

In dry-validation 0.12.2.. which I admit is pretty old ;)

Grant Shangreaux

@gcentauri

@ta dry isn't here anymore, its on zulip now https://dry-rb.zulipchat.com/register/

Tonni Tølbøll Lund Aagesen

@ta

oh, thanks

Sam Stickland

@samstickland

I'm struggling with the documentation.. how can I make this work in dry-types 1.2.x ? It's using an older syntax:

  module Types
    include Dry::Types(default: :nominal)

    CompactArray = Types::Coercible::Array.constructor { |vs| vs.map(&:presence).compact.map }

    SplittingCompactArray = Types::Coercible::Array.constructor do |vs|
      vs
        .flat_map { |v| v.is_a?(::String) ? v.split(',') : v }
        .map(&:presence)
        .compact
        .map
    end
  end

Grant Shangreaux

@gcentauri

@samstickland chat has moved to zulip https://dry-rb.zulipchat.com/

Alex Hayes

@alexhayes

Are there any docs regarding the differences between Types::JSON::DateTime and Types::JSON::Time and when you should use one over the other?

Grant Shangreaux

@gcentauri

@alexhayes this chat is dead. check the the topic, it moved to zulip

Alex Hayes

@alexhayes

Thanks Grant, I realised that after I posted.

Lenart Rudel

@lenart

Hey guys, I'm trying to wrap my head around the difference between

  optional(:age).filled(:integer, gt?: 18)
  optional(:age).maybe(:integer, gt?: 18)

To me this reads that age is optional in both cases and that when the value is present it should be typecasted as integer and be greater than 18. I Feels like the two statements are identical - or am I missing something?

Seb Wilgosz

@swilgosz

@lenart the latter one allows to pass NIL:

contract = MyContract.new
contract.call(age: nil, age2:nil)
#<Dry::Validation::Result{:age=>nil, :age2=>nil} errors={:age=>["must be filled"]}>

The optional keyword allows you to completely SKIP the key, so it would be valid for validator.call({}) because you can omit both of them. But if you pass any value, only one can be nil, and the other one needs to be present and castable to Integer.

Chau Duc Tai

@taigroddy

Hello guys,

Im using Dry::Transaction

May I can inherit?
For ex:

class ApplicationService
```
        include Dry::Transaction
```
class AdminService << ApplicationService (step :validation, step :check_active, step :privileges { another processing } )
class UserService << AdminService (step :validation, step :check_active, step :privileges { another processing })

I always have to repeat 3 steps

Chau Duc Tai

@taigroddy

like this:

   class AdminService << ApplicationService
         step :validation
         step :check_active
         step :privileges

        def validation; end
       def check_active; end
       def privileges; and
  end

    class UserService << AdminService
         step :validation
         step :check_active
         step :privileges

       def privileges; and
   end

could I only need to do

class UserService << AdminService
   def privileges; and
end

Chau Duc Tai

@taigroddy

remove 3 first lines of class UserService

Dorian Taylor

@doriantaylor

hey folks, i'm running into this again: dry-rb/dry-schema#335

Types::Constructor(URI) triggers &:uri?

Dorian Taylor

@doriantaylor

i get the deprecation error but would prefer a solution that wasn't setting Dry::Schema::PredicateInferrer::Compiler.infer_predicate_by_class_name false

ah never mind, /topic

Andrej Yaroshuk

@Codcore

Hello! Can I somehow set custom message for dry-validatiions pre-built matchers? Like:

      required(:email).filled(:string) { key.failure('Message') }

Where communities thrive

People

Repo info

Activity