e543d8bc5a
* Fix type keyword completions 1. In functions, type keywords were omitted. 2. In All context, no keywords were omitted. (1) fixes #28737 (2) removes 17 keywords that should not be suggested, even at the toplevel of a typescript file: * private * protected * public * static * abstract * as * constructor * get * infer * is * namespace * require * set * type * from * global * of I don't know whether we have a bug tracking this or not. * Change keyword filter in filterGlobalCompletion Instead of changing FunctionLikeBodyKeywords * Add more tests cases * Make type-only completions after < more common Because isPossiblyTypeArgumentPosition doesn't give false positives now that it uses type information.
39 lines
1,020 B
TypeScript
39 lines
1,020 B
TypeScript
/// <reference path="fourslash.ts" />
|
|
|
|
////const x = 0;
|
|
////type T = number;
|
|
////function f(x: number) {}
|
|
////function g<T>(x: T) {}
|
|
////class C<T> {}
|
|
|
|
////x + {| "valueOnly": true |}
|
|
////x < {| "valueOnly": true |}
|
|
////f < {| "valueOnly": true |}
|
|
////g < /*g*/
|
|
////const something: C</*something*/;
|
|
////const something2: C<C</*something2*/;
|
|
////new C</*C*/;
|
|
////new C<C</*CC*/;
|
|
////
|
|
////declare const callAndConstruct: { new<T>(): callAndConstruct<T>; <T>(): string; };
|
|
////interface callAndConstruct<T> {}
|
|
////new callAndConstruct<callAndConstruct</*callAndConstruct*/
|
|
|
|
for (const marker of test.markers()) {
|
|
if (marker.data && marker.data.valueOnly) {
|
|
verify.completions({ marker, includes: "x", excludes: "T" });
|
|
}
|
|
else {
|
|
verify.completions({ marker, includes: "T", excludes: "x" });
|
|
}
|
|
}
|
|
|
|
verify.signatureHelp({
|
|
marker: "callAndConstruct",
|
|
text: "callAndConstruct<T>(): string",
|
|
parameterName: "T",
|
|
parameterSpan: "T",
|
|
parameterCount: 1,
|
|
argumentCount: 1,
|
|
});
|