-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Salsa: "Implicit globals" leak into member completions but not global completions? #6654
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@billti how should we fix this?
|
the later is an problem when we guess things wrong: var x = {};
x.a = 0;
x.b = "string";
x.| The earlier seems like a more consistent approach. VSCode should show these completions as a different icon. the CompletionEntry.kind field should be the marker here, also CompletionEntry.sortKey should push these all to the bottom. |
@mhegazy we have already changed the icon in our latest: |
@RyanCavanaugh Did this fix scope variables leaking in to instance completions? I just got the latest vscode 0.10.10 and now see this type of polluted intellisense all over my js apps: I would only expect to see similar to this Source: class SomeClass {
constructor(param1, param2, param3) {
this.param1 = param1;
this.param2 = param2;
this.param3 = param3;
}
doSomething() {
}
}
var a, b, c, d, e;
var instance = new SomeClass(1, 2, 3); |
@billti thanks for the info. Is there a way to turn of this noise? |
@billti Is there any way to hide the extraneous identifiers? I don't see how |
From @alexandrudima on January 27, 2016 13:34
Testing #2218
IMHO member completions should get less suggestions than the global completions, not the other way around:
Copied from original issue: microsoft/vscode#2447
The text was updated successfully, but these errors were encountered: