We are implementing a debug adapter extension. While implementing breakpoint features, we found out there is no distinction between enabling/disabling breakpoints and adding/removing them when they are being sent through a setBreakpointRequest. In other words, whenever a breakpoint is disabled, this breakpoint is removed from the breakpoint list being sent via the setBreakpointRequest.
This causes an inconsistency, between what is viewed in the Breakpoints Window in VS Code and what is happening in the backend.
To resolve this issue, we would probably need the stored breakpoint list to use some attribute in the breakpoint type when enabling/disabling it rather than adding/removing the breakpoint altogether.
We are implementing a debug adapter extension. While implementing breakpoint features, we found out there is no distinction between enabling/disabling breakpoints and adding/removing them when they are being sent through a
setBreakpointRequest. In other words, whenever a breakpoint is disabled, this breakpoint is removed from the breakpoint list being sent via thesetBreakpointRequest.This causes an inconsistency, between what is viewed in the Breakpoints Window in VS Code and what is happening in the backend.
To resolve this issue, we would probably need the stored breakpoint list to use some attribute in the breakpoint type when enabling/disabling it rather than adding/removing the breakpoint altogether.