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
If the same thing (e.g. class, function) is exported in an entrypoint through both the default export and a named export, I'd expect the generated documentation to look the same regardless of which export has been defined first.
Preferably, if the same thing is exported in both the default and the named export, the default export should contain references to the named export, not the other way around.
Actual Behavior
TypeDoc will produce different documentation pages based on whether the default export is placed before or after the named export.
Search terms
default export, named export, reference
Expected Behavior
If the same thing (e.g. class, function) is exported in an entrypoint through both the default export and a named export, I'd expect the generated documentation to look the same regardless of which export has been defined first.
Preferably, if the same thing is exported in both the default and the named export, the default export should contain references to the named export, not the other way around.
Actual Behavior
TypeDoc will produce different documentation pages based on whether the default export is placed before or after the named export.
For the following code:
TypeDoc outputs:
while for this one:
it shows:
Steps to reproduce the bug
npm ci
npm run docs
docs-default-first
, generated usingdefaultFirst.ts
as the sole entrypoint,docs-default-last
, generated usingdefaultLast.ts
as the sole entrypoint.Environment
The text was updated successfully, but these errors were encountered: