JSDoc comments break indent

[j-f1]

What version of TypeScript are you using?
2.3.4

What version of typescript-eslint-parser are you using?
4.0.0

What code were you trying to parse?

/**
 * @a
 */
foo;

This code also breaks:

/**
 * @a
 */
/**
 * a
 */
foo;

What did you expect to happen?
No errors

What happened?

Expected indentation of 0 spaces but found 1. (indent)

None of these throw the error:

/**
 * a
 */
foo;

/**
 * @a
 */

/**
 * @a
 */

[w0rp]

I've been seeing this issue myself in my codebase. In some cases, we were able to disable the errors by using /*** for comments, so they won't be recognised as jsdoc comments, or by wrapping the jsdoc comments in eslint comments to disable the rule for those lines.

[JamesHenry]

I haven't had chance to dig into this at all yet, but it's possible you can use the new functionality in the indent rule to work around this: eslint/eslint#8594

[bradzacher]

what's the status of this? it's producing a lot of erroneous linting errors across my codebase.

[sarvaje]

@bradzacher if it is an option for you, you can use the rule indent-legacy until this issue is fixed

[JamesHenry]

Thanks for providing the alternative workaround, @sarvaje.

I am going to try and come up with a solution for this "integration" issue.

[JamesHenry]

I can no longer reproduce this issue with the latest dependencies involved. Please feel free to reopen if it is still an issue.

[Tarnadas]

It's still not resolved for me.

These are my dependencies:

    "typescript": "^2.6.2",
    "typescript-eslint-parser": "^12.0.0",
    "eslint": "4.15.0"

[bkotos]

This is not resolved for me either. Having the latest typescript-eslint-parser doesn't fix it.
My relevant dependencies:

    "typescript": "^2.6.1",
    "typescript-eslint-parser": "^12.0.0",
    "eslint": "^4.14.0",

[stanbluijs]

Having the same issue, is there any update on this?

"typescript": "^2.6.2",
"typescript-eslint-parser": "^12.0.0",
"eslint": "^4.16.0"

[benedictchen]

+1