Unnecessary parameter info for commas and opening parenthesis within strings

[NoelAbrahams]

Hi,

VS: 2013 Update 4 RC
TS: 1.3

Also occurs with ( and <

[johnnyreilly]

Complete aside @NoelAbrahams but what did you use to record and create the animated GIF? This could be useful to me!

Like the Throught for the Day BTW - I expect to hear you on Radio 4 soon. 😄

[NoelAbrahams]

@johnnyreilly, I think all credit to @heroboy for introducing this. See #895

[johnnyreilly]

Oooh that's amazing! I'm off to download now....

[DanielRosenwasser]

I've actually been discussing this with @JsonFreeman because typing those characters in tagged template strings also trigger this sort of behavior. I think the desired behavior can get a little complex, but it's doable.

[DanielRosenwasser]

@CyrusNajmabadi and @mhegazy, is there any way that we could introduce the concept of"hard", "soft", and "continuation" triggers?

Specifically:

• A "hard" trigger means that the user specifically requested signature help (Ctrl+Shift+Space).
• A "soft" trigger means that we are hinting to the language service to provide signature help (These would be the keys for (, ,, ```, }).
• A "continuation" trigger means that we were already showing signature help. A continuation trigger has higher priority than a "soft" trigger.

[JsonFreeman]

We already have two kinds of triggers (called Trigger and ReTrigger). I think what you are asking for is for the signature help query to also provide the trigger reason. In that case, if the language service encounters a comma inside a string literal, it would only show signature help on a ReTrigger, not a Trigger.