Skip to content

Possibility to handle remaining errors in catchTags #4784

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 8 commits into
base: next-minor
Choose a base branch
from

Conversation

akoenig
Copy link

@akoenig akoenig commented Apr 23, 2025

Type

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

Description

Sometimes, it’s necessary to recover from specific errors in catchTags, while still handling all other possible errors in a general way.

This PR is based on this Discord thread and introduces a possible function as a second parameter to catchTags, allowing you to handle all the other errors that are not explicitly specified.

An example:

import { Data, Effect } from "effect"

class A extends Data.TaggedError("A") {}
class B extends Data.TaggedError("B") {}
class C extends Data.TaggedError("C") {}
class D extends Data.TaggedError("D") {}

const program = Effect.gen(function* () {
  const types = [A, B, C, D];
  const Exception = types[Math.floor(Math.random() * types.length)];

  return yield* new Exception
}).pipe(
  Effect.catchTags(
    {
      A: (a) => Effect.succeed(a._tag),
      B: (b) => Effect.succeed(b._tag),
    },
    remaining => Effect.succeed(`remaining: ${remaining._tag}`) // C | D
  )
);

@akoenig akoenig requested a review from mikearnaldi as a code owner April 23, 2025 17:47
@github-project-automation github-project-automation bot moved this to Discussion Ongoing in PR Backlog Apr 23, 2025
Copy link

changeset-bot bot commented Apr 23, 2025

🦋 Changeset detected

Latest commit: 76e2fda

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 32 packages
Name Type
effect Minor
@effect/cli Major
@effect/cluster Major
@effect/experimental Major
@effect/opentelemetry Major
@effect/platform-browser Major
@effect/platform-bun Major
@effect/platform-node-shared Major
@effect/platform-node Major
@effect/platform Major
@effect/printer-ansi Major
@effect/printer Major
@effect/rpc Major
@effect/sql-clickhouse Major
@effect/sql-d1 Major
@effect/sql-drizzle Major
@effect/sql-kysely Major
@effect/sql-libsql Major
@effect/sql-mssql Major
@effect/sql-mysql2 Major
@effect/sql-pg Major
@effect/sql-sqlite-bun Major
@effect/sql-sqlite-do Major
@effect/sql-sqlite-node Major
@effect/sql-sqlite-react-native Major
@effect/sql-sqlite-wasm Major
@effect/sql Major
@effect/typeclass Major
@effect/vitest Major
@effect/ai Major
@effect/ai-anthropic Major
@effect/ai-openai Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@effect-bot effect-bot changed the base branch from main to next-minor April 23, 2025 17:47
@effect-bot effect-bot force-pushed the next-minor branch 3 times, most recently from e1a8749 to 0163ac2 Compare April 24, 2025 04:29
@effect-bot effect-bot force-pushed the next-minor branch 13 times, most recently from c0f49fb to ecaad91 Compare April 30, 2025 20:49
@effect-bot effect-bot force-pushed the next-minor branch 6 times, most recently from 768a4f2 to 7f658a7 Compare May 2, 2025 10:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Discussion Ongoing
Development

Successfully merging this pull request may close these issues.

2 participants