trailblazer-activity

trailblazer-activity copied to clipboard

seuros

When using task wrap you have no way to access the ID of the step

1

When using custom macros that return a Proc/Lambda, you have no access to the id when applying a task wrap. Because of this, the only way you can try and...

ChrisHampel

The internal `@id` given by `VariableMapping()` should be random and unique.

apotonick

yogeshjain999

Graph#outputs

1

Would it be more consistent to have `Graph(MyActivity).outputs` instead of `MyActivity.to_h[:outputs]`?

apotonick

CI: Drop unused sudo: false directive

3

See https://blog.travis-ci.com/2018-11-19-required-linux-infrastructure-migration for more details

olleolleolle

```ruby module Myactivity step a step Nested(Tyrant::Magicstep), success => d step c step Rescue(d), exception => myhandler step e ```

apotonick

``` task TaskWrap::Trace.method(:capture_return), id: "task_wrap.capture_return", before: "End.success", group: :end ```

apotonick

:replace etc don't inherit ID

2

Instead, you have to repeat `:id`, which is slightly inconvenient. ```ruby step :a, replace: :SomeID, id: :SomeID ```

apotonick

Specify Output => End wiring in Macro

3

What we do currently ``` step :validate, Output(:failure) => End(:invalid_params) step :find_user, Output(:failure) => End(:not_found) ``` it works, but is repeated in every CRUD Operation ideally, I would like to...

iJackUA