This project is read-only.

Latest VS 2012, TS, Web Essentials...but no JSDoc param hints

Topics: General
May 14, 2013 at 5:20 PM
First time poster, so hopefully I'm asking in the right forum.

Trying to figure out if I'm missing something here. I've got the latest VS 2012, Web Essentials 2.7, and TypeScript (via Node). No matter what, I can't get my @param JSDoc comments to show up in the intellisense.

For simple method defined like this:
* Repeat str several times. 
* @param str The string to repeat. 
* @param times How many times to repeat the string. 
repeatIt(str, times): string {
    return "hi";
If I then type "this.repeatIt" to see the intellisense, it shows the signature, and the "Repeat str several times", but neither of the @param docs.

Is there some setting or update I am missing that enables this?


May 14, 2013 at 10:10 PM
You're doing things correctly. This works as you expect with the latest Typescript bits in the develop branch sans Web Essentials. It is possible there is a bug here in 0.8.3 and/or Web Essentials but I don't have a machine with them in front of me to check at the moment.
May 14, 2013 at 10:26 PM
Thanks! Good to know it's not some stupid oversight on my part, I was kind of going crazy since it seems like it should "just work". Thanks, let me know what you're able to find out.

Just so I'm clear, is using the Web Essentials VS plugin discouraged? It seemed like a no-brainer to install it since it seemed to add a fair number of extra TS features.


May 15, 2013 at 1:38 AM
It appears to work correctly for me with 0.8.3 + VS2012 Ultimate.

Web Essentials is not discouraged by any means. It certainly has some very nice functionality. It simply isn't supported by us in an official sense. We don't have the resources to be constantly testing our new features against every new release of Web Essentials, especially as things conflict (ex it has its own version of the Compile On Save feature). We do check it out periodically and some folks on the team use it to varying degrees so hopefully it should never be completely busted but it's quite possible there are some bad interactions along the edges at any given time and whether we can spend time fixing them is generally a matter of where the root cause is and who is actually doing the 'wrong' thing.
May 15, 2013 at 3:09 PM
@brian428 - have you tried the official VS plugin for TypeScript rather than WebEssentials + the Node version? I'd be curious to see if that fixes the issue.
May 15, 2013 at 3:30 PM
I believe I have both the "TypeScript Plugin" installed as well as Web Essentials 2.7. The first thing I did after setting up VS was download and run the TypeScriptSetup. that I downloaded from the TS site. Only after this did I read about the additional features that Web Essentials adds, so I then installed Web Essentials 2.7 as well.

That said, I'm a bit of a VS noob and I don't see anything in the Tools > Add-In Manager or Tools > Extensions and Updates that seems to mention the TypeScript Plugin. Is there a place where I can look to confirm that VS is using the plugin? I could also just try re-running the .msi, I suppose.