Typing "/**/" should work

[ghost]

Issue Type: Bug

When I type ", [, (, or { it is automatically matched with ", ], ), or }. But typing "" or () will work by consuming the automatic match, so I don't end up with ()).
When I type /**/ I would expect that to be exactly the text I get, but instead I get /**/ */.

[mjbvz]

@rebornix @alexandrudima This is because we expand /*| to /**| */. Is there any way to tell VS Code to eat the next / that the user types, like we for for ) when completing ()?

[alexdima]

@mjbvz I don't believe it is the same case as a single character expansion.

We expand /**| to /**| */, i.e. we append */ after the cursor.

It is not clear to me how to possibly recover if the user meant to type literally and empty comment: /**/.

Perhaps we should not expand /**| to /**| */ as it is not 100% clear a JSDoc will follow. Perhaps we should do the smart things when pressing Enter, as that more clearly indicates a JSDoc comment.

[alexdima]

Let's track in #1966