docs: Clarify Option + andThen guidance in pipeline docs #1295
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.
Type
Description
This makes the guidance more consistent across docs and a little easier to apply in practice, especially for newcomers deciding between
Option,Effecterrors, andExit.It also aligns the pipeline docs with the
Eitherdocs, which already discourage usingEitheras an error type inEffectworkflows. The previousbuilding-pipelinesexample still modeled this pattern, so this update removes that inconsistency.Effect.andThensection inbuilding-pipelinesto focus onOptioninterop.Eitherexample with guidance on whenEitheris still useful at boundaries.option.mdxto consistently describe mixingOptionwithEffect.Related