I use hashes, but it's up to you. You also can define a custom step http://dry-rb.org/gems/dry-transaction/custom-step-adapters/, but this is advanced usage :)
the main point is that dry-transaction doesn't have a mutable state inside
txn = define_transaction do
custom_step_adapter 'step_1', using: :value_1
custom_step_adapter 'step_2', using: :value_2
map 'step_3'
end
txn.call(value_1: 1, value_2: 2)
def my_step(value_1)
value_1 + 1
end
def my_step(value_2)
value_2 + 1
end
def step_3(context)
context # { value_1: 2, value_2: 3 }
end
@pabloh for example^
@pabloh There a "context" object, we call it
options which is basically a hash, and passed from step to step (per default) http://trailblazer.to/gems/operation/2.0/#state-and-result
However, most operations don't need that, so the "human" interface is very simple and looks "global", but it isn't. It took months to design it
I imagine that this is something to do with dry-monads not being loaded?
how do I make the tests pass?
thanks
looks like
rake runs two rspec suites
what's going on there?
funny how that happens
@flash-gordon I’d like to revisit hash schema implementation in dry-types, and try to figure out a more flexible way for setting them up. This was brought up before by @Kukunin I believe, I was initially against it, but we start to see more use cases where a more flexible solution would be very useful. /cc @backus
ie now we need a symbolized hash which has strict semantics too, and we’re stuck :)
this is definitely something to figure out before 1.0.0
if we can come up with a flexible solution which is also fast, that would be awesome. Oh and the lib should still provide a bunch of common, built-in hash schema types
@apotonick I’ll let you know once I have something working with the new dry-v + dry-schema, and re rom, I reported an issue about reform/rom integration so we can discuss things there I guess
@flash-gordon I have a crash on latest master of
dry-struct. on the first attribute call.equalizer.instance_variable_get('@keys').concat(new_schema.keys)NoMethodError: undefined method `concat' for nil:NilClass
/Users/kukunin/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/bundler/gems/dry-struct-fbe71e6445a8/lib/dry/struct/class_interface.rb:78:in `attributes'
/Users/kukunin/.rbenv/versions/2.3.1/lib/ruby/gems/2.3.0/bundler/gems/dry-struct-fbe71e6445a8/lib/dry/struct/class_interface.rb:50:in `attribute'
/Users/kukunin/Sites/matic-www/gems/shift-domain/lib/shift/domain/attachment.rb:8:in `block in <module:Domain>'
yep. that's the reason. thanks
any plans to release dry-struct 0.2.2 with minor changes?
it seems that major changes are coming (already in master)
and next release will be 0.3
you're doing great job, though. thanks
@timriley After reading your series post in Icelab's blog, I've finally come to understand dry-container and dry-auto_inject etc gems and their usecases. Before that I read the docs in dry-rb site but couldn't fully understand the concepts. Wouldn't it be better if the documentation of dry-rb website also contains a
Thanks.
getting started guide that walks the newcomers through some storybased steps introducing new concepts on every chapter like you did in the series post of Icelab blog?Thanks.
Glad to hear you figured this stuff out via the blog posts though :)
Hi all. I ma trying to make custom rule it should look like this:
rule(variant_presence: [:variant_id, :sku]) do |variant_id, sku|
variant_id.filled? | (sku.filled? & Spree::Variant.where(sku: value(:sku)).any?)
end But i have +arel+ is not a valid predicate name error. I really cant find nothing about this in documentation.