I am building a complex Workshop application where I use functions with custom libraries to do the evaluation. I am raising a lot of User Facing errors if something goes wrong so that users can actually act and provide the missing information. When doing a function evaluation for calculating a variable, the error is just reflected in the return of the function but cannot be caught in any way.
My suggestions:
- provide the option when defining a function-derived variable to trigger a toast if a UserFacingError occurs.
- Add a variable transformation category for handling errors e.g. matching error messages with regex to then set other variable values that could be used to steer the UI e.g. disabling buttons or opening a dialogue