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 based on JSDoc only not working #28440

Closed
monavari-lebrecht opened this issue Nov 9, 2018 · 3 comments
Closed

IntelliSense based on JSDoc only not working #28440

monavari-lebrecht opened this issue Nov 9, 2018 · 3 comments
Labels
Duplicate An existing issue was already created

Comments

@monavari-lebrecht
Copy link

0
down vote
favorite
I am using a framework, that generates automatically properties for classes and even classes can be generated by a define function.

The problem in Visual Studio Code is, that the autocompletion is not working if properties or whole classes are only defined by jsdoc. Or am I wrong? In Webstorm this works.

Example:

/**
 * @description
 * A Person
 *
 * @class
 */
function Person(name) {
    /**
     * @description
     * Name of the person
     * @property {String}
     */
    this.name = name;

    /**
     * @description
     * Another Name of the person
     * @property {String}
     */
    this.anotherName = name;

    /**
     * @description
     * Another Name of the person
     * @property {String}
     * @name Person#AndEvenMoreNames
     */
}

var oPerson = new Person("Peter");
oPerson.

Webstorm now enables autocompletion for all 3 properties, whereas Visual Studio Code only shows autocompletion for name and anotherName.

With classes defined only in JS it is the same...

Is my JSDoc wrong or the settings in VSCode?

I've put that question on stackoverflow too: https://stackoverflow.com/questions/53115831/vscode-how-to-autocomplete-only-in-jsdoc-defined-properties-or-classes

@vscodebot vscodebot bot assigned mjbvz Nov 9, 2018
@mjbvz mjbvz transferred this issue from microsoft/vscode Nov 9, 2018
@mjbvz mjbvz removed their assignment Nov 9, 2018
@mjbvz
Copy link
Contributor

mjbvz commented Nov 9, 2018

Support for @property is tracked by #15715

@mjbvz mjbvz closed this as completed Nov 9, 2018
@mjbvz mjbvz added the Duplicate An existing issue was already created label Nov 9, 2018
@monavari-lebrecht
Copy link
Author

For "virtual" classes the problem exists as well...

/**
 * @description
 * A Person
 *
 * @class
 * @name Person
 */

var oPerson = new Per

The Person class is not recognized as well...

@monavari-lebrecht
Copy link
Author

so I dont think, that it is related to the duplicate issue, isnt it? It is more a problem, that JSDoc without code implementation is ignored...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Duplicate An existing issue was already created
Projects
None yet
Development

No branches or pull requests

2 participants