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
I guess because it only happens with declare module, which isn't that common (and was previously converted to namespaces). In our case, after some experimenting, I found creating a merged declaration file with declare module to be the best option.
Anyways, I just tried out your change and it works as expected. With that, I think I now also have a working setup for generating a nice looking documentation for primefaces/primefaces#12717 Thanks again for fixing this so quickly.
blutorange
pushed a commit
to blutorange/primefaces-js-refactor-test
that referenced
this issue
Nov 24, 2024
Search terms
type alias link reference declare module
Steps to reproduce the bug
Just tried your fix for #2778, works perfectly. Unrelated to that, though, I did notice another strange behavior regarding links to type aliases:
When you generate the docs, the type alias
Foo
in modulefoo
links to the modulebar
, instead of directly to the interfaceBar
.(Which also results in a missing reference when using
typedoc-plugin-merge-modules
, since, well, the module does not exist anymore as it was merged).Interestingly, this only happens when using an import type. Importing the symbol first seems to work:
It also seems to happen with
declare module "name"
, but not when using separate filesbar.ts
andfoo.ts
.Expected Behavior
TypeDoc should link directly to the referenced type.
Actual Behavior
TypeDoc links to the the module containing that type.
Environment
6.8.0-35-generic #35-Ubuntu x86_64 x86_64 x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: