Add condition, hitCondition, and logMessage to the Breakpoint type

Open

#596 opened on Feb 24, 2026 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 48/100

Issue type: Feature
Clarity: Clearly specified
Activity status: Stale
Domain: api

Research direction

Start by locating the Breakpoint and SourceBreakpoint type definitions and compare their existing fields, using the linked Debug Adapter Protocol specification for context. Add the three optional fields proposed in the issue and verify that the protocol definition remains consistent with the documented request and response types.

Written by the indexing model from the issue text.

Description

under-discussion

Problem
The SourceBreakpoint type (request side) includes condition, hitCondition, and logMessage, but the Breakpoint type (response/event side) does not. This means when a debug adapter sends a breakpoint event, the client cannot determine whether the breakpoint is a logpoint or conditional breakpoint.

Consequence: Logpoints sent via breakpoint events render as regular breakpoints in the UI — losing the logpoint icon and confusing users. Conditional breakpoints similarly lose their condition decoration.

Proposed Change
Add three optional fields to the Breakpoint type, mirroring SourceBreakpoint:

interface Breakpoint {
// ... existing fields ...
condition?: string;
hitCondition?: string;
logMessage?: string;
}

Rationale
Symmetry: line and column already round-trip between SourceBreakpoint and Breakpoint. condition, hitCondition, and logMessage should too.
Backward compatible: All fields are optional — existing adapters and clients are unaffected.
Enables correct rendering: Clients can use logMessage presence to render logpoints (◇) vs breakpoints (●), and display conditions in hover/detail views.
Unblocks AI usecase: In developing AI capabilities for debugging, logpoints and conditional breakpoints are particularly requested features as agents can easily leverage advanced breakpointing techniques.

Dominant language: HTML
Stars: 1.8k
Forks: 173
Avg merge: 7d 7h
Merged PRs (30d): 2

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

`Array.initialize` and `Array.repeat` throw on a negative count Open

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

gren-lang/core#167 · Opened Sep 25, 2026
fix(pg-meta): schemas.update and schemas.remove DO blocks fail when a name contains "$$" Open

external-issue to-triage

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

supabase/supabase#50882 · Opened Sep 24, 2026
wkt: `WKTFieldMask.paths` is an immutable `public let paths: [String]` with no default `init(paths: [String] = [])` or `.with(_:)` helper, preventing in-place mutation Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

googleapis/google-cloud-swift#1151 · Opened Sep 24, 2026
SqliteSaver.list(filter=...) silently misses nested metadata values containing non-ASCII text Open

external

Difficulty 2/5 1-3 hours Newbie friendliness 65/100

langchain-ai/langgraph#9074 · 1 comment · Opened Sep 24, 2026
Correct FileCitationBody.index documentation to describe its position in output text Open

documentation specification

Difficulty 1/5 Under an hour Newbie friendliness 90/100

openai/openai-openapi#584 · Opened Sep 24, 2026

More Backend & API Design issues