eclipse-cdt-cloud / eclipse-cdt-cloud/cdt-gdb-vscode
Logpoint does not evaluate expressions inside curly braces {}; outputs literal placeholder instead of variable value
- Dominant language
- TypeScript
- Stars
- 26
- Forks
- 31
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 2
Description
## Description
When using a logpoint in VS Code, the log message does not correctly replace the expression enclosed in curly braces {} with its evaluated value. Instead, the original placeholder text is printed literally.
## Example
- Log condition set to: testA variable = {var}
- Expected output: testA variable = 42 (assuming var equals 42)
- Actual output: testA variable = {var} (no substitution occurs)
plugin version = v2.8.0
Contributor guide
Research direction
Start by locating the logpoint handling and message-formatting entry points in the TypeScript extension. Reproduce the issue with a log condition such as `testA variable = {var}` and inspect any existing tests covering logpoint output. Done means expressions in curly braces are evaluated and the output contains the variable value rather than the literal placeholder.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100