Repository navigation
Conversation
crowlKats
commented
Oct 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #426
Fixes #427
A type imported from a file that isn't a documented entrypoint, but which another entrypoint re-exports under a different name, was rendered as plain text:
Datainf's signature now links tob.ts/~/Foo.html.locationonImport.lookup_symbol_hrefuses that location to find the documented re-export via the reference index when the import source isn't a documented file. Member paths work too (Util.Options→Helpers.Options).js/types.d.tsmirrors the new field.The other two cases from the issues (
Foo.Datathrough an import, andimport { Data as Foo }alongside a localData) already worked on main; regression tests cover all of them.