aglinxinyuan opened a new issue, #7422: URL: https://github.com/apache/texera/issues/7422
### Task Summary `setupMonacoBreakpointMethods` is the one uncovered block in `CodeDebuggerComponent`. The existing spec deliberately stubs it out because the minimal editor mock cannot back a real `MonacoBreakpoint`, so neither of the two overrides it installs is exercised. **The glyph override** decides what the gutter shows: ``` exists && condition present -> monaco-conditional-breakpoint exists && no condition -> monaco-breakpoint hovering only -> monaco-hover-breakpoint ``` with `Boolean(condition?.trim())`, so a whitespace-only condition must not claim to be conditional, and the condition is looked up at `range.startLineNumber` — reading `endLineNumber` would attribute another line's condition to this glyph. **The mouse-down override** replaces the library's own handler. The `dispose()` before re-registering is load-bearing: two live handlers would add and immediately remove a breakpoint on a single click. A left click toggles, a right click opens the condition input instead (and only for a line that already has a breakpoint), and clicks below the last line or outside the gutter do nothing. Note for whoever picks this up: the stand-in editor is easiest to write as a `Proxy` that answers any unstubbed `on*` listener with an inert disposable, rather than trying to track which events `monaco-breakpoints` subscribes to — it calls `onDidChangeCursorPosition` among others. ### Task Type - [ ] Refactor / Cleanup - [ ] DevOps / Deployment / CI - [x] Testing / QA - [ ] Documentation - [ ] Performance - [ ] Other -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
