New issue
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
Not resolving {@link NaN}
#4
Comments
Resolving within Currently, resolver links only work for types. If you had |
Ah, I see. Thanks for clearing that up! |
Unblocked on TypeDoc's side now, but would require |
With v3.0.1, we now recognize |
Environment:
Windows 11
Node.js v16.16.0
typescript v4.7.4
typedoc v0.23.10
typedoc-plugin-mdn-links v2.0.0
Maybe I'm just an idiot, but I can't figure out how to actually use this - I've been manually linking to MDN myself so far whenever appropriate.
I figured it was supposed to just auto-resolve
{@link NaN}
-style links (as well aslinkcode
andlinkplain
variants) that it knows about into MDN links, so I added the following to my docs just to test it out:And after running
npx typedoc --logLevel Verbose
I get this output:And sure enough the 'NaN' text in the docs is not transformed into a link to the MDN page for
NaN
.To me it seems like the plugin isn't even attempting to resolve this link, or it would have printed the following message to the console (as per your
index.ts
):[typedoc-plugin-mdn-links]: Failed to resolve type: NaN
I chose the start with
NaN
since it is included in yourglobalObjects.ts
, but for the life of me I can't figure out how to get it to work. Help pls? 💜The text was updated successfully, but these errors were encountered: