You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the chat, a user named AlexDixon is discussing an issue encountered when upgrading the Effect Typescript library from version 3.2.5 to the latest version. Specifically, they noticed a change in the behavior of tryPromise when it is used with one argument: the error message isn't propagated in the latest version, while it was in the older version.
Michaelarnaldi responds by noting that without a catch, the error becomes an UnknownException, and they express uncertainty about why the message is no longer being carried.
Key Takeaways:
There is a change in error propagation behavior in tryPromise between Effect library versions 3.2.5 and the latest.
When not using a catch, errors might be transformed into UnknownException.
The exact reason for the loss of the error message in new versions is unclear from the messages.
Summary
In the chat, a user named AlexDixon is discussing an issue encountered when upgrading the Effect Typescript library from version 3.2.5 to the latest version. Specifically, they noticed a change in the behavior of
tryPromise
when it is used with one argument: the error message isn't propagated in the latest version, while it was in the older version.Michaelarnaldi responds by noting that without a catch, the error becomes an
UnknownException
, and they express uncertainty about why the message is no longer being carried.Key Takeaways:
tryPromise
between Effect library versions 3.2.5 and the latest.UnknownException
.Discord thread
https://discord.com/channels/795981131316985866/1326266797455970407
The text was updated successfully, but these errors were encountered: