fix(storage): expose status and statusCode on StorageError base class #2018
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
Contributor
|
@7ttp can you please rebase your PR with latest |
7ttp
force-pushed
the
fix/storage-error-statuscode-type
branch
from
b7fec22 to
d1a3111
Compare
mandarini
approved these changes
Jan 22, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary
Exposes
statusandstatusCodeproperties on the baseStorageErrorclass for TypeScript compatibility.Problem
Storage operations return errors typed as
StorageError, butstatusandstatusCodeproperties only exist on theStorageApiErrorsubclass.This causes TypeScript errors when users try to access these properties without casting.
Solution
Add optional
status?: numberandstatusCode?: stringto the baseStorageErrorclass. Backwards compatible - no breaking changes.Related