Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
Spencer Goh
@dymaxionuk

@flash-gordon , I've figured it out! seems like a clash between the mixin Dry::Transaction::Operation as soon as I include that it breaks. That Operation mixin includes...

Dry::Matcher.for(:call, with: Dry::Matcher::ResultMatcher)

which wraps :call and clashed with the Do wrapping.

Tim Riley
@timriley
@dymaxionuk hmm, we have an integration test in dry-matcher to ensure it works with dry-monads do notation IIRC
Spencer Goh
@dymaxionuk
Hi Tim, that's suprising... cos I just typed out an example and flattened all the Dry::Transaction::Operation includes into the top level of my class
and it blew up with that ResultMatch
Tim Riley
@timriley
Hmm, could you please file an issue with your gem versions and example case?
Spencer Goh
@dymaxionuk
class MyOp
  include Dry::Monads::Result::Mixin
  include Dry::Matcher.for(:call, with: Dry::Matcher::ResultMatcher)
  include Dry::Monads::Do.for(:call)

  def call
    _should_fail_fast = yield one('hello')
    Success(:yesyesyes)
  end

  def one(param)
    Failure(:nonono)
  end
end

MyOp.new.call
Nikita Shilnikov
@flash-gordon
it can fail if you include modules in the wrong order
Spencer Goh
@dymaxionuk
I'll raise an issue, it might be some clash with the versions I'm using...
Nikita Shilnikov
@flash-gordon
first do, then matcher
this is the right way
Spencer Goh
@dymaxionuk
aah but problem is I'm extending a base class MyOperation
and so the matcher gets included first
Nikita Shilnikov
@flash-gordon
it won’t work
you may want to use included or something like this as a workaround
Spencer Goh
@dymaxionuk
it's ok I'll push up the Do wrap higher up the chain in my base class.
it migjht silently catch other ppl off guard in a similar way if they are usiung Dry::Transaction::Operation and not conscious of the ordering
thanks for help guys
Tim Riley
@timriley
tbh I wonder about the value of Dry::Transaction::Operation in the first place
Spencer Goh
@dymaxionuk
yeah agreed - the monads cover all, and give far more flexibility.
I'm in teh process of ripping out dry-web / dry-web roda (since they dont do much anyway other than some pre config + deprecated) just ripped out dry-transactio from my project (it's slow also) and just removing operations... all I need is the Matcher realy..
and that's clean... and far more powerful composing actions with fmap bind or etc.
the biggest limitation of transactions imo, is of having to chain the parameters from step to step.... so step 1 has 5 params.. of which onky 2 are pertinent for step 2, and diff 2 are useful for step 3 etc... end up passing through in hash, most of the unused params
seems kinda pointless... and once you have the DO notation, the usefulness of step: adapters goes away
Tim are you thinking of deprecating Dry::Transaction one day?
Tim Riley
@timriley
@dymaxionuk No, dry-transaction will remain, it’s useful for many things
How have you found it to be slow?
Viet (Drake) Tran
@tiev
@dymaxionuk with functional objects style, the object interface is simple, you can compose instead of inherit a base class
I use dry-transaction for an importing CSV process and see no slowness
Spencer Goh
@dymaxionuk

Not slow per se, and unlikely issue in real world, but there was a page was linked off the dry-* website, where someone had done some perf tests... and shown that transactions were n factor slower than pure monads.. but then you get all the other benefits... hooks, notifications etc.

Personally not that useful to me anymore for what I wanna do...

a side issue relating to dry-system / Container , when config.auto_register is used, by default the AutoRegistrar will register a block taht creates a new instance.
i'd like to register a single instance of a class - (I have some stateless ext api adapter classes) that are used to call other services - i dontn really want to instantiate on each container resolution
woudl be nice to have a the option to pass a hash to that configuration
```
auto_register = { 'lib/stuff' => :instantiate, 'lib/singlestuff' => :singleton }
Mario Viapiano
@emeve89
Hello everyone, I've been using dry-container & dry-auto_inject to, of curse, avoid to reference dependencies in some classes (as part of the process of applying clean/hexagonal architecture). The thing is that when I use dry-auto_inject, my use cases now depend on the container that lives in a outter layer. What do you think about that? how do you "mix" the use of auto-inject & the guidelines of the clean architecture, for example?
Spencer Goh
@dymaxionuk
or :memoize option I guess is really waht I'm looking to pass through
but the auto register config can't pass that down into the container.register call.
Shawn Anderson
@shawn42
Hi everyone. Thanks for making such a great suite of libraries. I really appreciate all the work and time you've all put in.
Nikita Shilnikov
@flash-gordon
Thanks :heart:
Shawn Anderson
@shawn42
I do have a question the best way to use the List monad over a collection of Try results. The list is built dynamically, then I want to create a List out of the results. When I try to traverse them, it complains about it not being typed. I've tried adding .typed calls, but am not sure what the correct type is. Try did not work. (apologies if this is something simple; I'm pretty new to monads)
Is there a way to use the List monad to collect all my Failure objects? traversing only seems to return the first error. Warning: I'm fairly new to monads.
oh man, gitter is being flaky.. it didn't tell me that last message actually sent...
Hi everyone. Thanks for making such a great suite of libraries. I really appreciate all the work and time you've all put in.
what I'm shooting for is: something like M::List::Validated[M::Success(1), M::Failure("boom 2")].typed(M::Result).traverse => Failure(List<Result>["boom 1", "boom2"])
Philip Arndt
@parndt

Hey folks, we've been testing Zulip as a Gitter replacement for the last few days. So far it feels really great and we'd like more people to sign up and check it out. We did not decide yet if we want to switch but it's likely that we will, because of this please sign up and let's chat there whether you like it or not.

You can sign up right here: https://dry-rb.zulipchat.com/register/

If you haven't heard about Zulip, it's an OSS communication platform. Something between a chat and email, with a unique communication model based on streams and topics. The company behind it was acquired by Dropbox, but they open sourced the project back in 2015. Its development is very active and it looks promising in general.

Check out Why Zulip here: https://zulipchat.com/why-zulip/

you could try Zulip @shawn42 ^

Shawn Anderson
@shawn42
Thanks @parndt I'll check it out
Philip Arndt
@parndt
gitter's being super janky for me too
Piotr Solnica
@solnic
yes, especially that Gitter is acting WEIRD lately
Nikita Shilnikov
@flash-gordon
Yeah, that’d be the best way :)
Piotr Solnica
@solnic
like messages from @shawn42 are disappearing for me, then re-appearing but in a different order lol
Shawn Anderson
@shawn42
so zulip is kind of a google wave rebirth? ;)
also, now that you are all here.. any ideas on the best way to collect my failures using a list monad? or is that not the correct usage?