Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

intellisense doesn't support jsdoc namespaces #17749

Closed
mjbvz opened this issue Aug 11, 2017 · 1 comment
Closed

intellisense doesn't support jsdoc namespaces #17749

mjbvz opened this issue Aug 11, 2017 · 1 comment
Labels
Duplicate An existing issue was already created VS Code Tracked There is a VS Code equivalent to this issue

Comments

@mjbvz
Copy link
Contributor

mjbvz commented Aug 11, 2017

From @wehrstedt on August 11, 2017 7:29

  • VSCode Version: 1.14.2
  • OS Version: Windows 10 1703

Intellisense doesn't support jsdoc namespaces. If I create a namespace with

/** @namespace */
var myModule = {};

and create a type inside this namespace like

/**
 * @memberof myModule
 * @typedef {object} myType
 * @property {string} prop1
 */

the intellisense doesn't work if I annotate a variable like this:

/** @type {myModule.myType} */
var myVar;

Instead, if I annotate my variable like this, the intellisense works correct, but the type definition is not correct anymore:

/** @type {myType} */
var myVar;

This is the complete script:

/** @namespace */
var myModule = {};

/**
 * @memberof myModule
 * @typedef {object} myType
 * @property {string} prop1
 */

/** @type {myModule.myType} */
var myVar;
myVar. // intellisense doesn't work

/** @type {myType} */
var myVar2;
myVar2. // intellisense works

_Copied from original issue: Microsoft/vscode#32291_
@mjbvz mjbvz self-assigned this Aug 11, 2017
@mjbvz mjbvz added Domain: JSDoc Relates to JSDoc parsing and type generation VS Code Tracked There is a VS Code equivalent to this issue and removed javascript labels Aug 11, 2017
@mjbvz mjbvz removed their assignment Aug 18, 2017
@mhegazy
Copy link
Contributor

mhegazy commented Aug 29, 2017

Duplicate of #14233

@mhegazy mhegazy marked this as a duplicate of #14233 Aug 29, 2017
@mhegazy mhegazy closed this as completed Aug 29, 2017
@mhegazy mhegazy added Duplicate An existing issue was already created VS Code Tracked There is a VS Code equivalent to this issue and removed Domain: JSDoc Relates to JSDoc parsing and type generation VS Code Tracked There is a VS Code equivalent to this issue labels Aug 29, 2017
@microsoft microsoft locked and limited conversation to collaborators Jun 14, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Duplicate An existing issue was already created VS Code Tracked There is a VS Code equivalent to this issue
Projects
None yet
Development

No branches or pull requests

2 participants