Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Result injection works really well to chain units of work together, mapping state via a sequence of
Input -> Output
transitions.However, the common scenario, once this has been built will be to encapsulate those smaller units of work with a
GroupProcedure
to hide the details of that state transition. At the moment, this is totally possible, but it does require unnecessary boiler plate, which we can remove.Essentially, we want to be able to do something like this:
Those two "bind" APIs will use observers to set the
input
andoutput
properties to the equivalent of the property on the receiver.