Skip to content

Conversation

@maciejziemichod
Copy link
Contributor

Type

  • Refactor
  • Feature
  • Bug Fix
  • Optimization
  • Documentation Update

Description

This makes the guidance more consistent across docs and a little easier to apply in practice, especially for newcomers deciding between Option, Effect errors, and Exit.

It also aligns the pipeline docs with the Either docs, which already discourage using Either as an error type in Effect workflows. The previous building-pipelines example still modeled this pattern, so this update removes that inconsistency.

  • Clarify the Effect.andThen section in building-pipelines to focus on Option interop.
  • Replace the previous Either example with guidance on when Either is still useful at boundaries.
  • Fix wording in option.mdx to consistently describe mixing Option with Effect.

Related

  • Related Issue #
  • Closes #

@vercel
Copy link

vercel bot commented Feb 10, 2026

@maciejziemichod is attempting to deploy a commit to the Effect Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant