dry-rb/chat

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

Daniel Gollahon

@dgollahon

that last one is a little awkward, yeah

Piotr Solnica

@solnic

well, it’s just not done yet (hence no docs too)

Daniel Gollahon

@dgollahon

but the first case seems potentially useful. i'll have to tinker with it.

yeah

totally understand

Piotr Solnica

@solnic

this is tricky stuff so it’s taking some time

Daniel Gollahon

@dgollahon

yeah, definitely

Piotr Solnica

@solnic

schemas have all sorts of properties, so it’s not just “use inheritance Luke!”

Daniel Gollahon

@dgollahon

but good to know there's an effort about it.

haha, yeah.

Piotr Solnica

@solnic

well, we just need to come up with an API :)

because internals are ready

Daniel Gollahon

@dgollahon

and "use inheritance Luke!" is also not inherently simple.

cool

Piotr Solnica

@solnic

that too :)

schema rules is just an array with rules, so we can append stuff, prepend stuff, compose with others, whatever we want

and since input processors are decoupled, this doesn’t affect the rules at all

furthermore, message compilation is decoupled too, so we can easily tune message settings for a schema that inherits rules from multiple other schemas that have different message settings :)

Daniel Gollahon

@dgollahon

neat, seems great. just time to do some API pondering.

seems like some of the harder parts will be if you have collisions

where both schema A and B operate on key foo.

Piotr Solnica

@solnic

we can do stuff like [a_rules.select { |r| r.name == :foo } + b_rules.select { |r| r.name == :foo }].reduce(:and)

errrr s/select/detect/

this stuff is crazy flexible so we can either do this, or make it configurable, or raise an error, dunno :)

Daniel Gollahon

@dgollahon

yeah. i would expect you could inadvertently get contradictory rules with an and. but maybe that's just your fault and ohwell :P

might be less surprising to raise an error. but i don't know, there may be a reasonable alternative.

Juanma Cervera

@jmcervera

Hi, A question about testing.
I'm developing a dry-system project, where my functional classes are registered in the app container.
I instantiate the objects in specs through the container as I do in the app.
How should I instantiate the subject object when I want to mock some of the dependencies,
with mocks or lambda functions to avoid for example go to the database through a repository?
Should I instantiate the object with new and not use the DI?
Is there a way to mock only some of the dependencies and get DI work for the others?

Piotr Solnica

@solnic

@jmcervera https://discuss.dry-rb.org/t/how-to-unit-test-service-using-dry-auto-inject/88/4?u=solnic

just use .new + kwargs (it’s the default constructor type in autoinject)

Juanma Cervera

@jmcervera

@solnic Thanks :smile:

Sergei Novikov

@droptheplot

Hi there! Looks like a have a similar questions but don't know where to start. I'm using containers in my application and currently calling them like container['somenamespace.somecontainer'].call within my specs. The questions is how to use auto_inject inside specs?

Jānis Miezītis

@janjiss

Hey folks, I created a gem main purpose of which is to map data from unformated hash (In my case from CSV rows) and turn it to some usable domain objects and to add dry-types as a basis for type checks. https://github.com/janjiss/massager

Piotr Solnica

@solnic

@janjiss oh cool I’ll check it out. thanks for sharing

Jānis Miezītis

@janjiss

@solnic On which time zone are you? Are you in Krakow or in US atm?

Just curiosity - Since your work hours look more like US, but under profile there is Krakow :D

Piotr Solnica

@solnic

@janjiss US atm

Christopher Dennl-Ortega Arrieta

@cdennl

@solnic Is it allowed to have multiple predicates( My::Predicates ) statements in the config block auf a schema?

Piotr Solnica

@solnic

@cdennl it’s config.predicates = YourPredicates since 0.9.x

or 0.8.0 O_o can’t remember exactly

oh and no, it doesn’t support more than one predicate module, at least not yet

Christopher Dennl-Ortega Arrieta

@cdennl

it is predicates(...) in 0.9+ :) and thank you I saw that only one is working at the moment

Piotr Solnica

@solnic

Ah right, I kept it eventually. Sorry, too much on my mind :)

Michał Gutowski

@CucumisSativus

Hey guys, in dry-types is there built-in way to make your own type to behave like a Maybe type?

Nikita Shilnikov

@flash-gordon

@CucumisSativus wdym by saying "behave like"?

Michał Gutowski

@CucumisSativus

@flash-gordon that it will return None if nothing is there and returns object if needed

s/needed/present

Nikita Shilnikov

@flash-gordon

yeah, but it will be wrapped with Some. dry-t has optional types ootb, so you can have your value or nil, wo wrapping it with a monadic interface

Krzysztof Wawer

@wafcio

I am reading dry-validation docs and sometimes I see require(:name).filled and sometimes I see require(:name).value(:filled) what is difference between these two syntax ?

Krzysztof Wawer

@wafcio

moreover sometimes you are using filled and filled?

Christopher Dennl-Ortega Arrieta

@cdennl

@solnic Why do I get a exception on this?

rule( check_comment_on_reject: [ :is_accepted, :comment ] ) do |is_accepted, comment|
          is_accepted.false? > comment.filled?
        end

in `block (3 levels) in <class:CreateSubmissionReview>': undefined method `then' for false:FalseClass (NoMethodError)
    from /usr/local/rvm/gems/ruby-2.3.1/gems/dry-validation-0.9.5/lib/dry/validation/schema/value.rb:95:in `instance_exec'
    from /usr/local/rvm/gems/ruby-2.3.1/gems/dry-validation-0.9.5/lib/dry/validation/schema/value.rb:95:in `rule'

Where communities thrive

People

Repo info

Activity