Skip to content

Documentation for built-in types only works once #2179

Closed
Closed
Documentation for built-in types only works once#2179
Assignees
MikhailArkhipov
Labels
area-intellisenseLSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc.bugIssue identified by VS Code Team member as probable bugimportantIssue identified as high-priority
Milestone
Aug 2018

Description

@brettcannon
Brett Cannon (brettcannon)
opened on Jul 17, 2018

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

Activity

  1. ImageBrett Cannon (brettcannon)
    added
    bugIssue identified by VS Code Team member as probable bug
    area-intellisenseLSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc.
    needs PR
    upstream-language server
    on Jul 17, 2018

  2. CodySchrank commented on Jul 27, 2018

    @CodySchrank
    Cody Schrank (CodySchrank)
    on Jul 27, 2018

    Also happening to me with custom types

  3. ImageBrett Cannon (brettcannon)
    added
    importantIssue identified as high-priority
    on Aug 2, 2018
  4. ImageMikhail Arkhipov (MikhailArkhipov)
    self-assigned this
    on Aug 9, 2018
  5. ImageMikhail Arkhipov (MikhailArkhipov)
    added this to the Aug 2018 milestone on Aug 9, 2018

  6. MikhailArkhipov commented on Aug 10, 2018

    @MikhailArkhipov
    Mikhail Arkhipov (MikhailArkhipov)
    on Aug 10, 2018

    microsoft/PTVS#4623

  7. ImageMikhail Arkhipov (MikhailArkhipov)
    closed this as completedon Aug 10, 2018
  8. Imagelock
    locked as resolved and limited conversation to collaborators on Sep 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area-intellisenseLSP-related functionality: auto-complete, docstrings, navigation, refactoring, etc.bugIssue identified by VS Code Team member as probable bugimportantIssue identified as high-priority

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions