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

Autocomplete issue: the first parameter is missing, and the property does not work #229

Closed
naeco2008 opened this issue Nov 15, 2017 · 3 comments
Labels
area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster

Comments

@naeco2008
Copy link

naeco2008 commented Nov 15, 2017

Environment data

VS Code version: 1.18.0
Python Extension version: 0.8.0
Python Version: 3.5.3
OS and version: Windows 10

Actual behavior

Two issues:

  1. when i mouse-hover a function, i can see the intellisense of this function. The problem is that the first parameter is missing. You can see the behavior from the below picture. The 'Text' parameter is missing from the function signature.

image

  1. When i mouse-hover some function, i cannot see any intellisense information. For example, when i hover 'id', i will see the following information:

image

however, i defined it like below, i don't know why the documentation for this property does not work.
image

Thanks for the help,
-Neil

@brettcannon brettcannon added info-needed Issue requires more information from poster area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. bug Issue identified by VS Code Team member as probable bug labels Nov 15, 2017
@brettcannon
Copy link
Member

For the missing initial argument, can you provide some sample code that demonstrates the problem?

As for the property issue, this is probably related to #210 .

@naeco2008
Copy link
Author

it looks the first issue is because i didn't set 'self' as the first parameter.
For the second one, i just rewrote them by using @Property. They work now.

But when i test the intellisense, i found sometimes it works well, sometimes it does not work suddenly. Is there someway i can debug the vscode-python to check what is wrong?

Thanks,
-Neil

@brettcannon
Copy link
Member

It depends on how far you want to go with the debugging. 😄 Actually running the extension under VS Code itself so you can debug it actually isn't difficult (see our CONTRIBUTING.md file or the VS Code docs itself on how to do it).

As always, sample code that triggers the problem is the most helpful.

Anyway, glad you figured things out!

@lock lock bot locked as resolved and limited conversation to collaborators Jul 12, 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 info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

2 participants