Suggestions for examples related to Arrow's integration docs #24
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.
This PR updates the Arrow integration documentation, focusing on demonstrating multiple bind operations. The aim is to show how Akkurate handles validations involving more than one operation.
The previous example with a single
bind
not consuming its result is usually considered an antipattern. In general, binding is only helpful inside aneither
block if there is more than one value to bind, and the second and further operations are somehow dependent on the results of previous operations.Here, we assume that for some reason, you should not attempt to validate an
author
unless you have previously validated abook
—still not the best example. The examples can be improved to show an actual use case of dependent monadic operations. Also, the examples may be expanded to includeRaise
vs. usingeither
blocks and the use of context-receivers.