Function and instruction breakpoint log message
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 48/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- json
- Área
- api
Línea de trabajo
El issue identifica las definiciones de esquema de FunctionBreakpoint e InstructionBreakpoint; encuentra esas definiciones en el esquema del protocolo y compara sus propiedades de breakpoint existentes. Añade el campo logMessage propuesto a ambos y verifica después que ambos esquemas lo expongan de forma coherente.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
There is not really any reason for them to not support logMessage field. This was raised in #114, but that post includes different issues as well.
"FunctionBreakpoint": {
"type": "object",
"description": "Properties of a breakpoint passed to the `setFunctionBreakpoints` request.",
"properties": {
"name": {
"type": "string",
"description": "The name of the function."
},
"condition": {
"type": "string",
"description": "An expression for conditional breakpoints.\nIt is only honored by a debug adapter if the corresponding capability `supportsConditionalBreakpoints` is true."
},
"hitCondition": {
"type": "string",
"description": "An expression that controls how many hits of the breakpoint are ignored.\nThe debug adapter is expected to interpret the expression as needed.\nThe attribute is only honored by a debug adapter if the corresponding capability `supportsHitConditionalBreakpoints` is true."
},
+ "logMessage": {
+ "type": "string",
+ "description": "If this attribute exists and is non-empty, the debug adapter must not 'break' (stop)\nbut log the message instead. Expressions within `{}` are interpolated.\nThe attribute is only honored by a debug adapter if the corresponding capability `supportsLogPoints` is true.\nIf either `hitCondition` or `condition` is specified, then the message should only be logged if those conditions are met."
+ }
},
"required": [ "name" ]
},
"InstructionBreakpoint": {
"type": "object",
"description": "Properties of a breakpoint passed to the `setInstructionBreakpoints` request",
"properties": {
"instructionReference": {
"type": "string",
"description": "The instruction reference of the breakpoint.\nThis should be a memory or instruction pointer reference from an `EvaluateResponse`, `Variable`, `StackFrame`, `GotoTarget`, or `Breakpoint`."
},
"offset": {
"type": "integer",
"description": "The offset from the instruction reference in bytes.\nThis can be negative."
},
"condition": {
"type": "string",
"description": "An expression for conditional breakpoints.\nIt is only honored by a debug adapter if the corresponding capability `supportsConditionalBreakpoints` is true."
},
"hitCondition": {
"type": "string",
"description": "An expression that controls how many hits of the breakpoint are ignored.\nThe debug adapter is expected to interpret the expression as needed.\nThe attribute is only honored by a debug adapter if the corresponding capability `supportsHitConditionalBreakpoints` is true."
},
+ "logMessage": {
+ "type": "string",
+ "description": "If this attribute exists and is non-empty, the debug adapter must not 'break' (stop)\nbut log the message instead. Expressions within `{}` are interpolated.\nThe attribute is only honored by a debug adapter if the corresponding capability `supportsLogPoints` is true.\nIf either `hitCondition` or `condition` is specified, then the message should only be logged if those conditions are met."
+ },
"mode": {
"type": "string",
"description": "The mode of this breakpoint. If defined, this must be one of the `breakpointModes` the debug adapter advertised in its `Capabilities`."
}
},
"required": [ "instructionReference" ]
},
- Lenguaje dominante
- HTML
- Estrellas
- 1.8k
- Forks
- 173
- Merge medio
- 7 d 7 h
- PR fusionados (30 d)
- 2
Preparar el entorno
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de microsoft/debug-adapter-protocol
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
microsoft/debug-adapter-protocol#633 · 1 comentario ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 42/100
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
microsoft/debug-adapter-protocol#599 · 8 reacciones ·
-
under-discussion
Dificultad 2/5 1-3 horas Aptitud para principiantes 48/100
microsoft/debug-adapter-protocol#596 · 9 comentarios ·
Todos los issues de microsoft/debug-adapter-protocol
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
SciML/Evolutionary.jl#182 ·
Los mantenedores suelen responder en 1 día
-
Missing GLM modelsAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
simonw/llm-mistral#43 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
rossoctl/context-guru#346 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
prime-radiant-inc/evener#2883 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
GoogleChromeLabs/project-sesame#216 ·
Los mantenedores suelen responder en 12 días