Open
Description
openedon Aug 8, 2024
🔎 Search Terms
AllowUnresolveNames, "preserve type nodes"
🕗 Version & Regression Information
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about AllowUnresolvedNames and preserve types
⏯ Playground Link
💻 Code
interface A {
foo: import("./doesntexist.js").Foo;
get bar(): import("./doesntexist.js").Foo;
}
class B implements A {
// Trigger completion: "implement interface A" display this completion:
// Actual:
// foo: any;
// get bar(): any {
// throw new Error("Method not implemented.");
// }
// Expected:
// foo: import("./doesntexist.js").Foo;
// get bar(): import("./doesntexist.js").Foo {
// throw new Error("Method not implemented.");
// }
}🙁 Actual behavior
Triggering completion uses any instead of the unresolved type.
🙂 Expected behavior
Completion should be the unresolved type instead of any
Additional information about the issue
Found in PR #59440
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment