`valid-types`: Handle inline imported TypeScript types

[yvele]

Motivation

Maybe related to #145

I'm using JavaScript (not TypeScript), but I still want to import TypeScript type in inline fashion.

Current behavior

Using:

/**
 * @returns {import("@slack/web/api").ChatPostMessageArguments}
 */

or

/**
 * @typedef {import("@slack/web/api").ChatPostMessageArguments} ChatPostMessageArguments
 */

Triggers the following error:

error Syntax error in type: import("@slack/web/api").ChatPostMessageArguments jsdoc/valid-types

Desired behavior

I want the ESLint JSDoc plugin to consider the inline TypeScript import as valid (although coding in JavaScript).

Note that Visual Studio code automatically created the @returns {import("@slack/web/api").ChatPostMessageArguments} so I consider it as valid.

Alternatives considered

/* eslint-disable jsdoc/valid-types */
/**
 * @returns {import("@slack/web/api").ChatPostMessageArguments}
 */
/* eslint-enable jsdoc/valid-types */

🤷

Any better workaround?

[brettz9]

Do you have settings: {jsdoc: {mode: 'jsdoc'}} set? It should instead be either omitted or explicitly set to the default of settings: {jsdoc: {mode: 'typescript'}}.

This mode is for the TypeScript flavor of JSDoc, not necessarily for TypeScript syntax, so you can use it inside of JavaScript files. The "jsdoc" mode is for the original https://jsdoc.app syntax only.

[yvele]

How yeah right I was using jsdoc mode. I've removed it (implicit typescript mode) and everything works fine.

Thank you @brettz9 ❤️