We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Typedoc should generate one namespace entry
Typedoc generates two entries
export namespace NS { export type T = string; } /** * @namespace */ export const NS = { property: 'blah', };
=> namespace NS with only T in it => namespace NS with property in it
I also found a related bug
export type NS = { foo: string }; /** * @namespace */ export const NS = { property: 'blah', };
=> This will create a Namespace named NS, with a foo property in it. => It seems @namespace is ignored
The text was updated successfully, but these errors were encountered:
Declaration merging is really annoying and full of weird edge cases...
The second example seems to be working as intended to me. TypeDoc creates a namespace + a type, as expected.
Sorry, something went wrong.
Declaration merging is really annoying and full of weird edge cases... The second example seems to be working as intended to me. TypeDoc creates a namespace + a type, as expected.
It creates the type and the namespace but the content of the namespace is wrongly generated.
Well, that's weird... I saw there was one property, didn't notice the name was wrong!
574363f
Fix @namespace property discovery
@namespace
4863952
Resolves #2364
No branches or pull requests
Search terms
Expected Behavior
Typedoc should generate one namespace entry
Actual Behavior
Typedoc generates two entries
Steps to reproduce the bug
=> namespace NS with only T in it
=> namespace NS with property in it
I also found a related bug
=> This will create a Namespace named NS, with a foo property in it.
=> It seems @namespace is ignored
Environment
The text was updated successfully, but these errors were encountered: