Jake Bailey
Jake Bailey
You could copy the bundled stubs to the `typings` directory (the one it warns about not existing) and see if changes. Note that I don't think we would differ in...
Is this a dupe of #276 (or vice versa), then? The analysis is split between them, but preferably we'd merge if they're the same.
The tooltip from the issue is a signature help (where we omit "(function)" since it's a signature, so must be a function). Maybe we have some lingering docstring inconsistency?
VS Code has a thing called "on enter rules" which are intended to do indention when you enter a new block. These rules are statically declared by a language provider...
We could ask them to set: ```json { "[python]": { "editor.formatOnType": true } } ``` Manually. It's just not super discoverable.
Is this entirely a completion problem, or should there be a change in our enum handling code to disallow this? `this` isn't defined in the enum stub, so it seems...
I got a few wires crossed and completely missed that `this` was the enum member by the time I finished my thought. I'm not sure what all is special cased...
At the moment, this is intended behavior. You can opt-in to workspace/library indexing by enabling the hidden option: ``` "python.analysis.indexing": true ``` Can you try it and see if this...
Thanks for the feedback. I think for your completion comment, that's #1055; we're currently working on ways to refine the massive number of completions that indexing produces (so many that...
It does, Ctrl+. does that in VS Code.