Doxygen formatting support

[TClawson]

Feature request: When typing /** above a function header, it would be great to auto-fill a standard doxygen comment template including @brief, parameters, and return descriptions. It should also include basic formatting such that if the cursor is inside of a comment block like this, hitting return and adding a new line should create a new line pre-pended by *.

[asl]

@TClawson You are writing When typing /** above a function header, so which LLVM component would be responsible for this? It seems that it is IDE responsibility for whatever IDE you are using.

[llvmbot]

@llvm/issue-subscribers-clangd

Author: Taylor Clawson (TClawson)

Feature request: When typing `/**` above a function header, it would be great to auto-fill a standard doxygen comment template including `@brief`, parameters, and return descriptions. It should also include basic formatting such that if the cursor is inside of a comment block like this, hitting return and adding a new line should create a new line pre-pended by ` *`.

[Endilll]

clangd seems to be the closest component here, but I'm not sure if this in scope for it.

[HighCommander4]

For the second part of the request:

It should also include basic formatting such that if the cursor is inside of a comment block like this, hitting return and adding a new line should create a new line pre-pended by *.

we have clangd/clangd#174 on file.

For the first part, I think that's in scope as well, we have other Doxygen-specific issues on file such as clangd/clangd#529.

[Endilll]

Thank you, @HighCommander4!
I'm closing this in favor of the issues you mentioned.

[HighCommander4]

Apologies for the confusion, I meant that doxygen-specific feature requests are in scope for clangd as a product because we have another one (clangd/clangd#529), not that this feature request is covered by clangd/clangd#529.

clangd/clangd#529 is about hovers; the request here to "auto-fill a standard doxygen comment" is more of a code completion feature (or onTypeFormatting perhaps -- the details need to be nailed down), so I think it makes sense to keep this issue open.