Skip to content

Commit 7743416

Browse files
authored
fix: clarify ContinuedEvent.allThreadsContinued (#514)
Fixes #513
1 parent 155d2bb commit 7743416

File tree

2 files changed

+3
-2
lines changed

2 files changed

+3
-2
lines changed

changelog.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@ sectionid: changelog
88

99
* 1.70.x
1010
* Clarify how `StackTraceArguments.format` applies
11+
* Clarify the default behavior of `ContinuedEvent.allThreadsContinued`
1112

1213
* 1.69.x
1314
* Clarify the flow diagram to start a debug session

debugAdapterProtocol.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -249,7 +249,7 @@
249249
},
250250
"allThreadsContinued": {
251251
"type": "boolean",
252-
"description": "If `allThreadsContinued` is true, a debug adapter can announce that all threads have continued."
252+
"description": "If omitted or set to `true`, this event signals to the client that all threads have been resumed. The value `false` indicates that not all threads were resumed."
253253
}
254254
},
255255
"required": [ "threadId" ]
@@ -1673,7 +1673,7 @@
16731673
"properties": {
16741674
"allThreadsContinued": {
16751675
"type": "boolean",
1676-
"description": "The value true (or a missing property) signals to the client that all threads have been resumed. The value false indicates that not all threads were resumed."
1676+
"description": "If omitted or set to `true`, this response signals to the client that all threads have been resumed. The value `false` indicates that not all threads were resumed."
16771677
}
16781678
}
16791679
}

0 commit comments

Comments
 (0)