Nick Sutterer
Nick Sutterer
"Fail early" is basically a hidden additional left track. "Early success" is the pendant on the right side! :grimacing:
Do note that there _is_ an inflection API and a visual editor to render diagrams, yet. This works by rendering JSON which is then converted to HTML5. This issue here...
Oh, hey @TylerRick !!! More like `Developer.visualize(..)`, I am a big fan of the `render` method, it looks shitty but is much better than not knowing anything about the flow....
@mensfeld Did you know that `finder` is coming up or is this purely coincidentally? :open_mouth:
This is actually possible already! You can do ```ruby def MyMacro { task: task, Trailblazer::Activity::DSL.Output(..) => Trailblazer::Activity::DSL.End(..) } end ``` I leave this open so I don't forget to document...
Ah, oh sorry, I forget these are aliased haha! :beers: ? Yes!!!!!!!!!!!!!!!!!!
This is documented here https://trailblazer.to/2.1/docs/activity#activity-macro-api-options :beers:
Also, custom wirings from the original step declaration (e.g. `Output(:failure) => "some ID"`) are not copied. Again, this is not a bug, but inconvenient when trying to leverage the whole...
It would also be cool being able to only override, say `:input` ```ruby fail Disposable::Merge::Property::Scalar.method(:merge_value_into_a), replace: :write_a, input: ->(ctx, **) { ctx[:value] = nil; ctx }, output: ->(ctx, **) {...
Actually, this exception could be prevented in 99% of the cases if we had a compile time check when adding a `Subprocess` that has unwired termini.