2

It's all in the title.

Category: Development
STATUS DETAILS
Planned
2022 Release Wave 2
Ideas Administrator

Thank you for this suggestion! This is supported in the up-coming 2022 release wave 2. You can already now try it out in the insider VSIX.

We have added new options to control whether the debugger should break on errors in try functions.

Instead of the old boolean *BreakOnError* setting in a launch.json connection setup, this now takes one of the following values: *[true, false, "None", "All", "ExcludeTry"]*

The behavior for each option is:
* false/None: Does not break on any errors.
* true/All: Breaks on all errors.
* ExcludeTry: Breaks on errors only if they occur outside of the context of a Try function.

As can be seen, "true" and "false" are retained for now for backwards compatibility. They map to "All" and "None", we recommend using latter going forward, and might obsolete true and false in a future version.

Comments

H

And somewhat related - Add a way to make GETLASTERRORTEXT ignore TryFunction errors as well.

Category: Development