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
I'm currently using LanguageExt and have encountered a challenge regarding exception handling within the map and mapAsync callback functions. While using these functions to transform collections, I've found it difficult to propagate exceptions from inside the callback to the outside context.
Problem Description
When an exception occurs inside a callback function provided to map or mapAsync, it seems that the exception is not easily propagated to the outside world. This makes it challenging to handle errors effectively and perform any necessary cleanup or logging.
Example Scenario
Here's a simplified example of what I'm trying to achieve:
Hello,
I'm currently using LanguageExt and have encountered a challenge regarding exception handling within the map and mapAsync callback functions. While using these functions to transform collections, I've found it difficult to propagate exceptions from inside the callback to the outside context.
Problem Description
When an exception occurs inside a callback function provided to map or mapAsync, it seems that the exception is not easily propagated to the outside world. This makes it challenging to handle errors effectively and perform any necessary cleanup or logging.
Example Scenario
Here's a simplified example of what I'm trying to achieve:
May I know how should I handle exception inside map()/mapAsync()?
The text was updated successfully, but these errors were encountered: