microsoft / microsoft/vscode-cpptools
Code blocks in triple slash Doxygen comments are formatted incorrectly
@Colengms ci sta già lavorando.
Dal 18/9/2026.
- Lingua principale
- TypeScript
- Stelle
- 6.2k
- Fork
- 1.7k
- Merge medio
- 14h 46m
- PR unite (30g)
- 61
Descrizione
Environment
- OS and Version: Windows 11 Enterprise version 10.0.26200
- VS Code Version: 1.127.0
- C/C++ Extension Version: 1.32.2
- If using SSH remote, specify OS of remote machine: N/A
Bug Summary and Steps to Reproduce
Bug Summary:
If you place a Markdown code block inside inside a Doxygen comment that uses /// at the start of each line, and that comment contains any Doxygen tag, and you hover over a symbol to view its documentation, then indentation and // at the start of lines inside the code block is stripped.
The same comment switched to use //! formats correctly.
Steps to reproduce:
Write a function with documentation such as the following:
/// Test function
///
/// Example:
/// ```
/// // This program does the thing.
/// int main() {
/// DoThing();
/// return 0;
/// }
/// ```
/// \param x Test parameter
void DoThing(int x);
Expected behavior:
When hovering over the symbol, the documentation should be rendered as
Test function
Example:
// This program does the thing int main() { DoThing(1); return 0; }Parameters:
x- Test parameter
Actual behavior:
The documentation renders like this instead
Test function
Example:
This program does the thing int main() { DoThing(1); return 0; }Parameters:
x- Test parameter
Removing the \param line or changing the comment style to //! results in the expected rendering.
Configuration and Logs
Occurs in a workspace that only contains a single .cpp file and no c_cpp_properties.json.
Other Extensions
No response
Additional context
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Valutazione
Questa issue non è ancora stata valutata.