`rich_click.rich_click` does not show up in auto-complete in VSCode
See original GitHub issueNot sure if this is an issue with my own VSCode setup, but for some reason, I am not getting proper autocompletions for rich_click
on lines after the import. As I type the import
I do get the expected completions, but after that, when using the imported module, they don’t show up.
Because the completion for rich_click.r
did not show rich_click
, I was confused for a moment.
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Autocompletion not working for external C++ library in VSode
I created a folder .vscode with the file c_cpp_properties.json (adapted from here). Now, if I right-click an a type coming from that library ......
Read more >Editing Python in Visual Studio Code
Add the location to the python.autoComplete.extraPaths setting and restart VS Code. Navigation. While editing, you can right-click different identifiers to take ...
Read more >Markdown editing with Visual Studio Code
Working with Markdown files in Visual Studio Code is simple, straightforward, ... A warning shown in the editor when linking to a file...
Read more >User and Workspace Settings - Visual Studio Code
Not all User settings are available as Workspace settings. ... The settings that show up will be configurable for that specific language, and...
Read more >Visual Studio Code and Unity
Visual Studio Code can replace MonoDevelop as the editor for Unity. ... If you are installing VS Code for the first time, you...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
No worries! Thanks for reporting, I suspect you won’t be the only person coming across this…
@ewels Ah, haha, my bad. In hindsight, that makes sense. Thanks for pointing that out!