Trigger Sequence /** causes extra */ to be generated and the comment block isn't fully generated.

Description

When using /** as the Trigger Sequence an extra */ is also generated because /* generates this. This doesn’t let the comment get fully generated as it blocks the parser (that is my guess.) If I change the Trigger Sequence to //* the extra */ isn’t generated and everything works fine.

This didn’t start happening until updated to version 1.35.0 of Visual Studio code. I also can not see a way to stop this extra */ from happening within Visual Studio Code.

Expected result

	/**
	 * \brief 
	 * 
	 * \param keyID 
	*/
	void PressedKey(const UInt32 &keyID)

Actual result

	/**
	 * \brief 
	 * 
	*/
	 */
	void PressedKey(const UInt32 &keyID)

[cschlosser]

Hi all,

thanks for the report.

This has actually been the case for quite some time now but previously we were able to overwrite and characters generated by VS Code. It seems now that the order of events changed and we can not rely on this. I will take a look at it and then see if we need a workaround for the /** style comments.

[hg-zt]

Found an easy workaround, add this line into your settings.json:

    "doxdocgen.c.triggerSequence": "///"

Now just type / three times and press return.

Note the trigger sequence is not necessarily same with the prefix of the generated comment.