[JSDoc/checkjs]: exported @typedef doesn't work with mapped types directly

[Hotell]

TypeScript Version: 2.9.1

Search Terms:

• checkJS
• JSDoc

Expected behavior:
following should work without errors:

• types.js

// @ts-check
export {}

/**
 * @typedef {Partial<{one:boolean} & {two:string}>} Test
 */

• index.js

// @ts-check
/**
 * @type {import('./types').Test}
 */
const test = {}

Actual behavior:

• types.js

// @ts-check
export {}

/**
 * @typedef {Partial<{one:boolean} & {two:string}>} Test
 */

• index.js

// @ts-check
/**
 * @type {import('./types').Test}
 */
const test = {}

exported @typedef definitions, which are using Mapped types transformations (Partial,...), will error out with cryptic error when they are imported via /** @type {import('./types).MappedTest}* to annotate a variable :

Although creating a variable which is typed via mapped type and exported as a token value works:

• types.js

// @ts-check
export {}

/**
 * @typedef {Partial<{one:boolean} & {two:string}>} Test
 */

/**
 * @type {Test}
 */
export var Test

• index.js

// @ts-check
/**
 * @type {typeof import('./types').Test}
 */
const test = {}

[weswigham]

@sandersn This seems to be fixed in master, so I assume one of your many refactorings to jsdoc handling in the last two weeks have squelched this bug. Should we add a regression test, or do you know if one of the tests you've added covers this scenario?

[sandersn]

Our test coverage is pretty bad right now, so I would add a test. In particular, I didn’t test typedef with Es2015 modules, that I can remember at least.

[Hotell]

Just to mention, It's not with es2015 modules , just type import via import()

[sandersn]

Yes, but it's imported from an es2015 module, which might have been the cause of the assert.

[RyanCavanaugh]

@Hotell just to clarify, is this fixed, or not?