Repository navigation
Meta issue for intellisense issues #539
Description
Meta issue to track what we would hope would be fixed by some potential work.
- [Performance of Code Completion for LARGE files Performance of Code Completion for LARGE files #23]
- [Import [SPACE] should auto-pop up list of possible imports Import [SPACE] should auto-pop up list of possible imports #395]
- [Go to definition for Python project does not work with relative imports Go to definition for Python project does not work with relative imports #274]
- [Intellisense doesn't autocomplete if package names are repeated in different packages Intellisense doesn't autocomplete if package names are repeated in different packages #178]
- [The intellisense is not work in this case The intellisense is not work in this case #181]
- [Very long usage of vscode make suggestion to lag sometime Very long usage of vscode make suggestion to lag sometime #166]
- [Intellisense for a module fails in the conditional block when same module used in the if-statement (works for if-not) Intellisense for a module fails in the conditional block when same module used in the if-statement (works for if-not) #142]
- [クラスメソッド株式会社 (@classmethod) decorators not being properly treated @classmethod decorators not being properly treated #499]
- [Intellisense doesn't autocomplete if package names are repeated in different packages Intellisense doesn't autocomplete if package names are repeated in different packages #178]
- [Indentation after inserting an argument and after a function call Improve auto-indentation behaviour #481]
- [Consider using a language server Consider using a language server #83]
- [RAM Consumption RAM Consumption #263]
Upstream
- [Wrong intellisense icons for variables. Wrong intellisense icons for variables. #117]
- [Problem of enum class auto-complete problem of enum class auto-complete #207]
- [parameter name hints do not recognize 3.6-style string formatting parameter name hints do not recognize 3.6-style string formatting #344]
Activity
gustavovalverde commentedon Feb 26, 2018
Hi guys, I've been trying to leave Sublime for VS Code, but the Go to Definition seems to work just on 'simple' projects, the Intellisense with Python doesn't find most definitions when nested inside folders, under subclasses, with site-packages, etc; most of this issues are affecting my migration to VS Code, as not even the Find all references is working, which in Sublime just hovering the Class shows all the references in the project.
I can confirm most of this issues Don Jayamanne (@DonJayamanne):
#720
#647
#494
#244
#231
#185
#626
#503
#316
There's a great repo to test Intellisense ability https://github.com/odoo/odoo (the one I'm working on)
In VSCode
As an example, the same project in Sublime:
MikhailArkhipov commentedon Mar 30, 2018
https://github.com/Microsoft/vscode-python/projects/7#card-8587079
luabud commentedon Nov 24, 2020
Closing as stale.