Skip to content

docs: add example for setBreakpoint() with a conditional statement - #35823

Merged
Trott merged 0 commit into
nodejs:masterfrom
copperwall:patch-1
Oct 29, 2020
Merged

docs: add example for setBreakpoint() with a conditional statement#35823
Trott merged 0 commit into
nodejs:masterfrom
copperwall:patch-1

Conversation

@copperwall

Copy link
Copy Markdown
Contributor

The node-inspect debugging client supports passing an optional third parameter as a string to be evaluated when the breakpoint is hit. If the condition evaluates to true in the current context, the breakpoint pauses execution, otherwise the execution continues.

This was raised as an issue in nodejs/node-inspect#68, but the client already supports that functionality, so I thought it'd be helpful to add it to the node documentation.

Checklist

@nodejs-github-botnodejs-github-bot added debugger doc Issues and PRs related to the documentations. labels Oct 26, 2020
@Trott
Trott requested a review from hybristOctober 27, 2020 13:41
Comment threaddoc/api/debugger.md Outdated
@Trott

Copy link
Copy Markdown
Member

Welcome @copperwall and thanks for the pull request! I left a suggestion, but it's totally optional. Looks good to me either way.

@hybristhybrist left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, potentially with Trott's suggestion.

@Trott

Copy link
Copy Markdown
Member

Landed in a3cc239

@Trott

Copy link
Copy Markdown
Member

Thanks for the contribution! 🎉

@TrottTrott closed this Oct 29, 2020
@Trott
Trott merged commit a3cc239 into nodejs:masterOct 29, 2020
targos pushed a commit that referenced this pull request Nov 3, 2020
The `node-inspect` debugging client supports passing an optional third
parameter as a string to be evaluated when the breakpoint is hit. If the
condition evaluates to `true` in the current context, the breakpoint
pauses execution; otherwise the execution continues.
This was raised as an issue in
nodejs/node-inspect#68, but the client already
supports that functionality, so I thought it'd be helpful to add it to
the node documentation.
PR-URL: #35823
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Jan Krems <jan.krems@gmail.com>
@targostargos mentioned this pull request Nov 3, 2020
BethGriggs pushed a commit that referenced this pull request Dec 8, 2020
The `node-inspect` debugging client supports passing an optional third
parameter as a string to be evaluated when the breakpoint is hit. If the
condition evaluates to `true` in the current context, the breakpoint
pauses execution; otherwise the execution continues.
This was raised as an issue in
nodejs/node-inspect#68, but the client already
supports that functionality, so I thought it'd be helpful to add it to
the node documentation.
PR-URL: #35823
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Jan Krems <jan.krems@gmail.com>
BethGriggs pushed a commit that referenced this pull request Dec 10, 2020
The `node-inspect` debugging client supports passing an optional third
parameter as a string to be evaluated when the breakpoint is hit. If the
condition evaluates to `true` in the current context, the breakpoint
pauses execution; otherwise the execution continues.
This was raised as an issue in
nodejs/node-inspect#68, but the client already
supports that functionality, so I thought it'd be helpful to add it to
the node documentation.
PR-URL: #35823
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Jan Krems <jan.krems@gmail.com>
@BethGriggsBethGriggs mentioned this pull request Dec 10, 2020
BethGriggs pushed a commit that referenced this pull request Dec 15, 2020
The `node-inspect` debugging client supports passing an optional third
parameter as a string to be evaluated when the breakpoint is hit. If the
condition evaluates to `true` in the current context, the breakpoint
pauses execution; otherwise the execution continues.
This was raised as an issue in
nodejs/node-inspect#68, but the client already
supports that functionality, so I thought it'd be helpful to add it to
the node documentation.
PR-URL: #35823
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Jan Krems <jan.krems@gmail.com>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docIssues and PRs related to the documentations.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@copperwall@Trott@hybrist@nodejs-github-bot