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 have a module where a type and function have the same name (as the function is used to create instances of the type). Recently, typedoc has begun resolving ambiguously-named references by picking one of the two at random. (Well, maybe it was already doing that, but its choice changed, from the one I wanted, to the one I didn't.)
Is there any way to tell TypeDoc, "no I want to {@link} the type, not the function?" I'd prefer to use TypeScript link resolution, but TypeScript appears to implicitly resolve such links by referencing both definitions. (i.e. both show up as a hover in VSCode, and "go to definition" brings up both).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I have a module where a type and function have the same name (as the function is used to create instances of the type). Recently, typedoc has begun resolving ambiguously-named references by picking one of the two at random. (Well, maybe it was already doing that, but its choice changed, from the one I wanted, to the one I didn't.)
Is there any way to tell TypeDoc, "no I want to
{@link}
the type, not the function?" I'd prefer to use TypeScript link resolution, but TypeScript appears to implicitly resolve such links by referencing both definitions. (i.e. both show up as a hover in VSCode, and "go to definition" brings up both).Beta Was this translation helpful? Give feedback.
All reactions