microsoft / microsoft/vscode-cpptools
Doxygen var command not parsed
Open
Nobody has claimed this yet.
enhancement
Feature: Doc comments
Language Service
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
Environment
- OS and Version: Windows 11 24H2
- VS Code Version: 1.99.3
- C/C++ Extension Version: 2.0.0
Bug Summary and Steps to Reproduce
Bug Summary: @var and \var are not recognized as doxygen command tokens.
Steps to reproduce:
- Create a doxygen-style comment
- Add a @var or \var command
- Bask in the lack of highlighting
- If you want to confirm your fears, use the inspect tokens command of vscode
Expected behavior:
@var and \var should be recognized as doxygen command tokens.
Configuration and Logs
{
"configurations": [
{
"name": "Win32",
"includePath": [
"${default}"
],
"defines": [
"_DEBUG",
"UNICODE",
"_UNICODE"
],
"windowsSdkVersion": "10.0.22621.0",
"intelliSenseMode": "windows-msvc-x64"
}
],
"version": 4
}
Other Extensions
No response
Additional context
No response
Contributor 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.
Research direction
Start by locating the Doxygen command token definitions in the TypeScript extension source and inspect how existing @ and \ commands are recognized. Reproduce the issue with a C++ Doxygen-style comment and VS Code's Inspect Tokens command. Done means both @var and \var are classified as Doxygen command tokens.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100