You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enums should be rendered correctly if exported via an object
Actual Behavior
There are two different issues depending on the way we write our enums:
If the enum is written in separate file, the enum is rendered as a variable.
If the enum is written in the same file, it is identified as an enum but the page is blank except the title.
Steps to reproduce the bug
enums.ts
/** * This is a custom enum that is exported as a constant object. * * @enum */exportconstCustomEnum={/** A */A: "A",}asconst;
index.ts
import{CustomEnum}from"./enums";/** * This is a second custom enum that is exported as a constant object. * * @enum */constCustomEnum2={
...CustomEnum,D: "D",}asconst;/** @namespace */exportconstExportedObject={
CustomEnum,
CustomEnum2
}
This renders like the following:
2025-08-25.at.13.30.43.-.Coffee.Orca.mp4
As you can see:
CustomEnum2 is identified as an enum but the dedicated page is blank.
Expected Behavior
Enums should be rendered correctly if exported via an object
Actual Behavior
There are two different issues depending on the way we write our enums:
Steps to reproduce the bug
enums.ts
index.ts
This renders like the following:
2025-08-25.at.13.30.43.-.Coffee.Orca.mp4
As you can see:
CustomEnum2is identified as an enum but the dedicated page is blank.CustomEnumis identified as a variable.Environment