Skip to content

EG-4747: make AlreadyClosedError part of the hierarchy of SDK errors - #432

Merged
ppicom merged 1 commit into
eg-4747-private-transportfrom
eg-4747-hierarchical-error
Sep 28, 2026
Merged

ppicom merged 1 commit into
eg-4747-private-transportfrom
eg-4747-hierarchical-error

Conversation

@ppicom

@ppicom ppicom commented Sep 28, 2026

Copy link
Copy Markdown
Contributor

Back when coding the Transport and AsyncTransport, we introduced a new error type that our users can depend on and code around: AlreadyClosedError.

Errors are part of the SDK's API. Hence, in this PR I am making that new error part of the "error hierarchy" that I introduced a few pull requests back.

This change gives more support to fine grained Exception control from our users: you can capture UnleashClientError and grab all errors from our SDK, you can catch Error (e.g. TransportError) and deal with a whole set of related errors, or just catch one specific error.


Stack created with GitHub Stacks CLI • Give Feedback 💬

@ppicom
ppicom added this pull request to stack #440 September 28, 2026 10:53

@sighphyre sighphyre left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ppicom
ppicom force-pushed the eg-4747-hierarchical-error branch from 36c6162 to 9a1da92 Compare September 28, 2026 13:21
@ppicom
ppicom merged commit 1163aa4 into main Sep 28, 2026
13 of 19 checks passed
@ppicom
ppicom deleted the eg-4747-hierarchical-error branch September 28, 2026 14:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants