Hmm, it's a surprise for me too. @jrieken any ideas?

I've also found function annotations to not be working

/**
 * @returns {string}
 */
function f() {
    return canvas1;
}

We ship different versions of TypeScript in the standalone editor and VS Code

Meaning if I just upgrade the monaco TypeScript support to the same version in VS Code it will start working? Or, meaning the stuff in VS Code is not compatible with Monaco?

Well if you're curious I added the monaco editor to http://webglfundamentals.org. All of the examples run in a codepen style editor using monaco. Every sample has this at the top

  /** @type {HTMLCanvasElement} */
  var canvas = document.getElementById("canvas");
  var gl = canvas.getContext("webgl");

If monaco supported type annotations like VSCode then from that both canvas and gl would support all the intellisense like functions.

If there's a way to make that work that would be great.

@jrieken is there any progress with this issue?

closing as dupe of #177

I'm confused how #177 relates to this. #177 is closed saying the project is now on TypeScript 2.1 but this issue, issue #203 still doesn't work.

Is there's a way to make it work? Or if not could you please re-open this issue?

I can confirm JSDoc annotations still don't work.

@jrieken Perhaps there is more to getting them work than updating to TS 2.1

Is there any way to hint Monaco of the type of a given function parameter dynamically (eg without modifying the editor source) ?
I tried dynamically creating a d.ts for a given function signature, but when you declare that function in the editor it treats it as an override, and ignores the type information I added.
See
http://stackoverflow.com/questions/43037243/provide-type-hints-to-monaco-editor

I have added a PR in monaco-typescript. The providers for monaco-editor are greatly simplified from the language features for vscode. In vscode there is now further abstraction away from the language services which also extractions the documentation and tags from the quick info and returns them from the hover provider.

@kitsonk I had a quick look at your PR ( microsoft/monaco-typescript#14 ), I don't think it actually fixes this issue, which is about having the Monaco know the type of a parameter from the JSDoc annotations, so that code complete / intellisense works on that parameter?

This works for me (without microsoft/monaco-typescript#14) on master. It is important to know that this is supported in JS files only and the we interpret files as JS when they have an uri-path that ending in .js like some/path/some/file.js. When no ending is available make sure to use the allowJs-compiler setting

The fix for this (microsoft/monaco-typescript@9b5c885) will be in the next release.

Cool. Just to confirm @jrieken, a and b will have code complete within the body of foo()?