JSDoc rule should not block arbitrary comments like /********/

[nomaed]

Problem

There are 2 prime examples of comments that confuse tslint JSDoc detection regex:
A separator:

class MyClass {
    public prop1;
    public prop2;
    /********************************************/
    constructor() { ... }
    public method1() { ... }
    public method2() { ... }
    /********************************************/
    private internal1() { ... }
}

and

/**************
 * my-file.ts *
 **************/

These can be used as visual separator or guides, and are definitely not JSDocs.
Was also reported in issue #1121 several months ago.

Solution

Instead of matching any /^\s*\/\*\*/, I suggest that when there are more than 2 asterisks in a row, it should not be tested as a JSDoc comment.
Thus, the regex is updated to /^\s*\/\*\*([^*]|$)/ which would accept /** followed by anything but another *.

matched as jsdoc

/** (space) */ // valid, empty
/**text */ // invalid
/**_ */ // invalid
/** (new-line) // valid
 */

not jsdoc

/***/
/*/
/*******/
/******
*******/

[jkillian]

This seems reasonable, thanks @nomaed!