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
Expected behavior:ts.ResolvedModuleWithFailedLookupLocations has a failedLookupLocations property which reports locations where the lookup was tried and failed.
Actual behavior:failedLookupLocations is marked @internal and thus not available in the public typings. This is in contrast to ResolvedTypeReferenceDirectiveWithFailedLookupLocations which does expose the failedLookupLocations, which leads me to believe this was an omission and not an intentional hiding of the field.
The text was updated successfully, but these errors were encountered:
alxhub
changed the title
ResolvedModuleWithFailedLookupLocations does not have failedLookupLocations
ResolvedModuleWithFailedLookupLocations does not publicly expose failedLookupLocations
Nov 30, 2018
#13139 explicitly marked failedLookupLocations as internal since its implementation detail. Infact I think it missed doing it for ResolvedTypeReferenceDirectiveWithFailedLookupLocations
Thank you for the information! In that case I would suggest maybe changing the type name, as it was surprising to me that a return value of type ResolvedModuleWithFailedLookupLocations did not actually have failedLookupLocations.
I also had this issue. My use case is a script that replaces "classic" imports with "node": I was trying to use ts.classicNameResolver's lookup locations for debug output.
TypeScript Version: 3.3.0-dev.20181130
Search Terms: ResolvedModuleWithFailedLookupLocations, failedLookupLocations
Expected behavior:
ts.ResolvedModuleWithFailedLookupLocations
has afailedLookupLocations
property which reports locations where the lookup was tried and failed.Actual behavior:
failedLookupLocations
is marked@internal
and thus not available in the public typings. This is in contrast toResolvedTypeReferenceDirectiveWithFailedLookupLocations
which does expose thefailedLookupLocations
, which leads me to believe this was an omission and not an intentional hiding of the field.Related Issues: #28276
The text was updated successfully, but these errors were encountered: