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
Can you specify what kind of use case you would like to support?
The current expectation is that whenever we use api/eval or equivalent, if any uncaught exception happens within a node, this exception is going to bubble up to the caller, so you could just wrap eval within a try/catch block.
If you want to an exception to be handled in a specific node you can also put the try/catch within the node definition.
A handler might decide to ignore the error and return a default value, or might collect multiple exceptions and throw them when finished. I'd prefer to centralize that w/o wrapping each node definition.
Being able to specify an exception handler would be very useful for my case.
The text was updated successfully, but these errors were encountered: