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
{{ message }}
Repository navigation
Using getTypeAtLocation on a const type reference creates a TS2304 diagnostic #34913
Because of caching, it has noticeable effects only when getSemanticDiagnostics is called after getTypeAtLocation.
It happens only when internal getDiagnosticsProducingTypeChecker method is used, but I think it still might be undesirable and would be an issue if #28584 would be merged.
Activity
RyanCavanaugh commentedon Nov 8, 2019
I was expecting this to be a problem of not calling
getTypeFromTypeNodeinstead, but it isn't