trailblazer-operation
trailblazer-operation copied to clipboard
trailblazer
Trailblazer's Operation implementation.
Also updates the checkout action and adds dependabot for GitHub Actions
Hey, We have a rails engine which defines business processes. A few other projects use this engine and make minor changes to the business processes, depending on the specific application....
## Class Dependencies * Class dependencies allow setting (temporary?) ctx variables for an operation. * Currently, those variables stay in the result ctx and hence bleed through to the outer...
Below line assumes that any `end_event` apart from `End::Success` would make `Result` unsuccessful. https://github.com/trailblazer/trailblazer-operation/blob/ddceff65a63ff7a72aa93cde3e2752d0d20d2512/lib/trailblazer/operation/railway.rb#L15 But as any custom event wouldn't mean the result is a failure, is it possible to...
Similar to https://github.com/trailblazer/trailblazer/issues/161 ## Problem By looking at an operation it's possible to tell what input it takes with a help of Contracts. Same can't be said about the output....
:wave: The README is rather... empty. :) Of course you can go to the trailblazer README and eventually find [the main documentation](http://trailblazer.to/gems/operation/2.0/) but at least a basic usage example like...
Supposedly many people want to stub nested OPs/ACTs. ```ruby expect(MyNestedOperation). to receive(:call).with("params" => {order_id: order.id, email: order.user.email) ``` We should explain how to do that in 2.1
Please see [Issue#63](https://github.com/trailblazer/trailblazer-operation/issues/63)
Hello @apotonick and the Trailblazer team! I think [Adding outputs](https://trailblazer.to/2.1/docs/activity#activity-wiring-api-output-adding-outputs) is a really powerful feature since it enables handling multiple outcomes during the operation run. I also enjoy using `operation.success?`...