JSDOC: Enums treated as namespaces in @typedef

[baybal]

Bug Report

🔎 Search Terms

enum
jsdoc
typedef

🕗 Version & Regression Information

• This is the behavior in every version I tried, and I reviewed the FAQ for entries about JSDOC

⏯ Playground Link

Playground link with relevant code

💻 Code

/** @enum {number} */
const Enums = {
  LALA: 1,
  LELE: 2,
  LULU: 3
}

/**
 * @typedef { { kind: Enums.LALA; size: number; } |
    { kind: Enums.LELE; width: number; height: number; } |
    { kind: Enums.LULU; radius: number; }} ZeZe
 */

🙁 Actual behavior

🙂 Expected behavior

Enums should not be treated as namespaces in JSDOC typedefs

[orta]

Enums isn't a type but a value, you want to use typeof Enums.LALA to pull out that string in a type context

[baybal]

Enums isn't a type but a value, you want to use typeof Enums.LALA to pull out that string in a type context

Exhaustive search will not work that way

Playground Link

[orta]

This would need some sort of as const or narrowing in JSDoc enums, a JSDoc enum is not the same as a TypeScript enum.

[baybal]

This would need some sort of as const or narrowing in JSDoc enums, a JSDoc enum is not the same as a TypeScript enum.

How to do it?

[typescript-bot]

This issue has been marked as 'Question' and has seen no recent activity. It has been automatically closed for house-keeping purposes. If you're still waiting on a response, questions are usually better suited to stackoverflow.