Support Doxygen arbitrary alias\tags settings (example: use '\par' instead of '\param')

[michelleangela]

We have configured Doxygen to use \par instead of \param, can that somehow also be supported (probably through some setting?).
Also, for some reason we put our Doxygen comments in between the function signature and the opening {. Doxygen parses that just fine ... will that work here as well?

Originally posted by @Boddlnagg in #658 (comment)

[michelleangela]

Also, for some reason we put our Doxygen comments in between the function signature and the opening {. Doxygen parses that just fine ... will that work here as well?

@Boddlnagg
I'm not sure if I understand what you mean by "in between the function signature and the opening {". Could you provide an example for this?

[Boddlnagg]

I'm not sure if I understand what you mean by "in between the function signature and the opening {". Could you provide an example for this?

Sure:

int foobar(int a)
/// \brief Foos the bar
/// \par a Something
/// \ret Something else (or not)
{
    return a;
}

(forgot to mention that we also have defined ret as an abbreviation for return)

[Boddlnagg]

To elaborate on the original request: We also have defined aliases \in, \out, and \inout for \param[in], \param[out] and \param[in,out], respectively. So I think the feature would need to support arbitrary alias settings. Or the VSCode extension needs to read and the original Doxygen config and evaluate the ALIASES definitions (https://www.doxygen.nl/manual/config.html#cfg_aliases), but I don't know if that is feasible.

[michelleangela]

@Boddlnagg

Thanks for the additional information.

Please note that our team prioritizes actions on product features with broad customer impact based on telemetry data and/or upvotes of feature requests.

[bobbrow]

It looks like there are two requests in here (additional tags, and comment position). Should we split it into two issues?
Also, does VS Code support collapsible sections in the tooltips? If so, we could potentially place the raw comment in there as a stop gap.

[J-Fields]

The formatted doxygen popup only recognizes \exception (not \throw or \throws), and \throws isn't even highlighted in the actual text.

[michelleangela]

The formatted doxygen popup only recognizes \exception (not \throw or \throws), and \throws isn't even highlighted in the actual text.

To display other Doxygen comment tags, set the setting C_Cpp.simplifyStructuredComments to false. This setting was added to resolve issue #5706.

[bobbrow]

This was addressed in 0.29.0