Skip to content
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

Wrong intellisense icons for variables. #117

Closed
DonJayamanne opened this issue Nov 13, 2017 · 3 comments
Closed

Wrong intellisense icons for variables. #117

DonJayamanne opened this issue Nov 13, 2017 · 3 comments
Assignees
Labels
area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. bug Issue identified by VS Code Team member as probable bug
Milestone

Comments

@DonJayamanne
Copy link

From @AndyBay on May 13, 2017 11:45

Environment data

VS Code version: 1.12.1
Python Extension version: 0.6.4
Python Version: 3.6.1
OS and version: Windows 10

Currently (as seen under), arguments are using the "variable" icon and class variables are using the "reference" icon.
intellisense_pre_change_1
intellisense_pre_change_2

If we take that the icons for intellisense in Typescript is correct, and do following changes to the out\client\providers\jediProxy.js file.

Before:

pythonVSCodeTypeMappings.set('value', vscode.CompletionItemKind.Value);
pythonVSCodeTypeMappings.set('variable', vscode.CompletionItemKind.Variable);

After:

pythonVSCodeTypeMappings.set('value', vscode.CompletionItemKind.Field);
pythonVSCodeTypeMappings.set('variable', vscode.CompletionItemKind.Property);

intellisense_post_change_1
intellisense_post_change_2

This change "fixes" it as far as I can tell, except for the fact that both "variables" and "class variables" use the same icon when instead they should be variables => Variables and class variables => Field.

Also found these comments in the file :)
// What's this, can't remember,
// Great example of poorly written code (this whole file is a mess)

Copied from original issue: DonJayamanne/pythonVSCode#958

@DonJayamanne
Copy link
Author

@AndyBay Apologies for never getting back to you on this.
I've been too busy looking into other issues and managed to over look something simple as this.
I'll look into this asap and try to include this into the next release.

@brettcannon brettcannon added awaiting 2-PR area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. bug Issue identified by VS Code Team member as probable bug labels Nov 14, 2017
@MikhailArkhipov
Copy link

MikhailArkhipov commented Dec 13, 2017

Jedi marks as value both variables and class members. In order to select the right icon the code may need additional hints from the current editing context.

@MikhailArkhipov MikhailArkhipov self-assigned this Dec 13, 2017
@MikhailArkhipov MikhailArkhipov added this to the March 2018 milestone Mar 10, 2018
@brettcannon brettcannon modified the milestones: March 2018, April 2018 Mar 27, 2018
@MikhailArkhipov
Copy link

Not going to deal with Jedi. New analysis engine should provide proper icons as it does in VS.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 11, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

3 participants