Rule jsdoc/no-undefined-types reports the type IterableIterator is undefined

[jaydenseric]

Expected behavior

The following:

// @ts-check

const messages = [];

for (const [index, message] of /** @type {IterableIterator<[number, unknown]>} */ (messages.entries())) {
  // …
}

Should not result in a rule jsdoc/no-undefined-types error.

Actual behavior

It results in the error:

The type 'IterableIterator' is undefined.

ESLint Config

{
  "extends": "plugin:jsdoc/recommended-typescript-error",
  "settings": {
    "jsdoc": {
      "mode": "typescript"
    }
  },
}

ESLint sample

// @ts-check

const messages = [];

for (const [index, message] of /** @type {IterableIterator<[number, unknown]>} */ (messages.entries())) {
  // …
}

Environment

• Node version: v20.0.0
• ESLint version v8.39.0
• eslint-plugin-jsdoc version: v43.1.1

[brettz9]

Closing as a dupe of #888 though feel free to comment further as needed.

[jaydenseric]

Why does the config plugin:jsdoc/recommended-typescript-error enable the jsdoc/no-undefined-types rule, when TypeScript itself reports errors for invalid JSDoc types? Is an easy fix for this issue to turn it off in the recommended TypeScript config, and regarding #888, to make the rule jsdoc/no-undefined-types a no-op in TypeScript mode?

[brettz9]

@jaydenseric : SGTM. How about you re-post your comment in #888 so others may chime in?