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

Documentation for built-in types only works once #2179

Closed
brettcannon opened this issue Jul 17, 2018 · 2 comments
Closed

Documentation for built-in types only works once #2179

brettcannon opened this issue Jul 17, 2018 · 2 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 important Issue identified as high-priority
Milestone

Comments

@brettcannon
Copy link
Member

If you launch VS Code and then type str(), you will get the documentation for the str type.

works

But if you type str() again on another line, like so:

str()
str()

you will get a message saying that "Documentation is still being calculated, please try again soon."

fails

@brettcannon brettcannon added bug Issue identified by VS Code Team member as probable bug area-intellisense LSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc. needs PR labels Jul 17, 2018
@CodySchrank
Copy link

Also happening to me with custom types

@brettcannon brettcannon added the important Issue identified as high-priority label Aug 2, 2018
@MikhailArkhipov MikhailArkhipov self-assigned this Aug 9, 2018
@MikhailArkhipov MikhailArkhipov added this to the Aug 2018 milestone Aug 9, 2018
@MikhailArkhipov
Copy link

microsoft/PTVS#4623

@lock lock bot locked as resolved and limited conversation to collaborators Sep 7, 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 important Issue identified as high-priority
Projects
None yet
Development

No branches or pull requests

3 participants