This plugin has limited use for TypeScript users that use interfaces and ES6 class syntax. Adding this would be great!
Related to #1

I have this method:

register(registerData: RegisterFingerprintData): Observable<{fingerToken: string} | OperationFailure> {..}

that can return an Observable of type {fingerToken: string} or OperationFailure. When I add Jsdoc comments I get the following comments:

• @param {RegisterFingerprintData} registerData
• @returns string

It says that returns an string but is not, it returns an Observable.

Thank you in advance!

Repro:
Have a class function like:

  static makeV1TableHeadings(headings) {

  }

Run "Add doc comments."
View the result:

  /**
   * @param  {} headings
   */

Note there's an extra space before the curly brackets.

e.g., in this class:

    export class TwoPageView extends Marionette.LayoutView<TwoPageModel> {
        private __leftContent: Content.ContentController = null;
        private __leftView: Page.PageView;

        private __rightContent: Content.ContentController = null;
        private __rightView: Page.PageView;

        public initialize() {
            logger.trace("initialize");
            this.listenTo(this, "view.updateParentController", this.__onSetParentController);
            this.listenTo(this.model, "change:split", this.__onSetPageSplit);

            this.addRegions({
                'leftRegion': '.js-region-left',
                'rightRegion': '.js-region-right'
            });
        }
    }

You can't add doc comments for "public initialize()" - no matter what I try it always says "Please select a TypeScript or JavaScript function signature"

when method contain return type as promise
then comments is not generated properly
Example :
/**
* @param {IRequest[]} test
* @returns Observable
* @description this method call API that returns lookup data.
*/
getUserDetails(test: IRequest[]): Observable<ILeaveLookUp | ErrorObservable> {

When there is already a doc comment above the function, but it only contains a description, no @param or @return tags, please add the tags to existing docblock

https://marketplace.visualstudio.com/items?itemName=stevencl.addDocComments

The Extension is causing an error

In your read me, you should include a link to the extension or at least say that it is named Add jsdoc comments. Had to look at your package config to figure it out.

I can make this change, and put a pr in if you dont have any attachment to styling.

It's possible to use this with .vue files?

The plugin incorrectly identifies the arguments of the function if an argument is taking a default value with a comma.

For instance, for separator: string = ',' it ends up detecting single quote ' as an argument.

/**
 * @param  {string} csvHeader
 * @param  {object[]} objs
 * @param  {string='} separator
 * @param  {} '
 * @returns string
 */
export function jsonArrToCsv(csvHeader: string, objs: object[], separator: string = ','): string

I'm a Sublime Text user, and one of the remaining features that's stopping the switch to VSCode for me is the DocBlockr extension.

It's essentially the same as this plugin, but it can be invoked from pressing TAB after /**:

/**tab
function say(word) {
    return word;
}

becomes:

/**
 * @param word
 * @return string
 */
function say(word) {
    return word;
}

Would it be possible to add this 'tab to complete' functionality to this extension for VSCode?

The regular constructors work, but the shorthand constructors create issues, input:

class Experiment {

  constructor(public  lines:           string[],
              private alignSymbols:    number,
              private firstSymbolOnly: boolean) {

  }  
}

Will cause the "add doc" command create this:

  class Experiment {
  /**
   * @param  {string[]} publiclines
   * @param  {number}   privatealignSymbols
   * @param  {boolean}  privatefirstSymbolOnly
   */
  constructor(public  lines:           string[],
              private alignSymbols:    number,
              private firstSymbolOnly: boolean) {

  }  
}

Notice the public/private are now part of a field name in the auto-generated documentation.

The very first typescript I attempted to generate jsdoc comments for:

/**

• @param {} {data
• @param {{data:T[]} columns}
• @param {ColumnSpecifications}} columns?
• @returns Shape
  */
  function analyze<T = unknown>({data, columns}: {data: T[], columns?: ColumnSpecifications}): {types: Record<string, ColumnType>, shape: Shape} {

The arguments are incorrect with the types and don't have correct syntax (The number of open/closed braces don't match). The return type is also incorrect.

OS: MacOS Version 10.14.5
VSCode Version 1.36.0

I used to be able to type: /** before my function like this:

/**
const myFunc = (myparams) => {}

then VSCode will immediately return:

/**
 * 
 * @param {*} myparams 
 */
const myFunc = (myparams) => {}

Now after the update of VSCode (I assume), it's very slow to pick up the comment. I normally have to quit VSCode and restart it to make it work, but it's very slow, it takes up to 2 seconds to return the JSDoc comment.

For parameters without types, it adds {any} but it's rather cumbersome to delete any first and then type.

Please consider just adding empty {} for unknown types. Thanks!

Generated comments are not indented the same as the function.

/**
 * @param  {any} someParam
 */
        function myFunc(someParam) {
            return true;
        }

I'd love to use this extension, but CTRL-ALT-D is mapped to switching desktops on Ubuntu.
I understand that any shortcut would clash for someone, so would it be possible to make the shortcut configurable in the workspace settings?

no idea how to add a signature and cannot use the package