Steve

Not sure how best to show the example I have as it's made up of a lot of small pieces of code in multiple places. I'm using capybara with cucumber(the...

I don't think `column_changes` is exactly synonymous, as the Sequel version is a hash arrays with old/new values for any changed fields, whereas disposable is a hash of true/false values....

What does the structure of this data look like? Is it just the name of the step that switched from right to left `results.failed_step`? Maybe the path that was taken...

Technically `Pipetree::Flow::Left` I assume? What do you mean/foresee having unlimited tracks doing to this? ```ruby [ [Pipetree::Flow::Left, ["contract.build", [ [Pipetree::Flow::Right, "operation.new"], [Pipetree::Flow::Left, "contract.validate"] ]]] ] ``` This would fit it...

How does https://github.com/trailblazer/trailblazer-operation/issues/6 play into the multiple tracks then? It's definitely not fail early, as it is supposed to leave the operation as a success. I suppose it could also...

I have this fixed my fork, and submitted pull request #21, but so far the maintainer hasn't pulled in the changes.

@apotonick I don't think these failures are the fault of anything I did, are they?

I think the biggest part of what @johnmeehan is suggesting is the `xxx_was`(AM) or `xxx_initial`(Sequel) methods. Just knowing that a field changed such as what disposable provides is not enough....

@fran-worley yes, of course that is possible to do, but it feels like it is more of a workaround than anything. This seems like such a common operation, that having...

It definitely wouldn't belong in reform-rails. Heck, I'm not even using Rails, and I need it. I think this aligns very much with the semantics of what one would expect...