-
Notifications
You must be signed in to change notification settings - Fork 931
Let the new coded exceptions from codecs-core
bubble up as-is through @solana/options
et al
#2244
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @steveluscher and the rest of your teammates on |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice. I'll also need to add this in some of codecs-core
, where the assertion error should also bubble up like so.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed. Also, TypeScript should prevent these errors so, unless you're DHH, it's unlikely to affect users.
f528a09
to
bb38bb1
Compare
de2848a
to
f7dd0d1
Compare
codecs-core
bubble up as-is through @solana/options
codecs-core
bubble up as-is through @solana/options
et al
Done, in this PR! |
bb38bb1
to
e4634c5
Compare
f7dd0d1
to
ea29eaa
Compare
Merge activity
|
…gh `@solana/options`
ea29eaa
to
9a1834c
Compare
🎉 This PR is included in version 1.91.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Because there has been no activity on this PR for 14 days since it was merged, it has been automatically locked. Please open a new issue if it requires a follow up. |
Summary
The developer will receive a
SOLANA_ERROR__CODECS_EXPECTED_FIXED_LENGTH_GOT_VARIABLE_LENGTH
and should be able to determine which thing was of the wrong type based on the line that threw that error. I don't think we need to rethrow/respecify the error here.Addresses #2118.