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
Copy file name to clipboardExpand all lines: crates/mq-dap/README.md
+6-5Lines changed: 6 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,11 +24,12 @@ Once connected to a DAP client:
24
24
2.**Conditional Breakpoints**: Only stop when an mq expression evaluates truthy, e.g. `x > 3`
25
25
3.**Hit Count Breakpoints**: Only stop once the hit count condition is met. A bare number, e.g. `3`, is shorthand for `hit_count >= 3`; otherwise it's evaluated as an mq expression with `hit_count` bound to the current hit count, e.g. `hit_count >= 3 && x == 1`
26
26
4.**Logpoints**: Log a message instead of stopping; uses mq's own `${expr}` string interpolation syntax, e.g. `x is ${x}`. `${self}` yields the current pipeline value and `${$VAR}` reads the environment variable `VAR`
27
-
5.**Start Debugging**: Launch the debugger with your query file
28
-
6.**Step Through Code**: Use step over, step in, and step out commands
29
-
7.**Inspect Variables**: Hover over variables or view them in the variables pane
30
-
8.**Watch Expressions**: Add mq expressions to your editor's watch pane to re-evaluate them against the current scope every time execution stops
31
-
9.**View Call Stack**: See the current execution stack in the call stack pane
27
+
5.**Exception Breakpoints**: Enable "Uncaught Exceptions" in your editor's breakpoints pane to automatically pause when a query raises an error that isn't caught by `try`/`catch`
28
+
6.**Start Debugging**: Launch the debugger with your query file
29
+
7.**Step Through Code**: Use step over, step in, and step out commands
30
+
8.**Inspect Variables**: Hover over variables or view them in the variables pane
31
+
9.**Watch Expressions**: Add mq expressions to your editor's watch pane to re-evaluate them against the current scope every time execution stops
32
+
10.**View Call Stack**: See the current execution stack in the call stack pane
0 commit comments