rich_click.rich_click does not show up in auto-complete in VSCode

[taranlu-houzz]

Not 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.

[taranlu-houzz]

I should add that the code all works properly (e.g. I am able to use rich_click.rich_click.* as expected).

[ewels]

Is this issue related to #57 ?

[taranlu-houzz]

Hmm, I'm not sure.. I don't really see how the *args/**kwargs issue mentioned would be related, but maybe?

[ewels]

Right, sorry - skim reading a bit too quickly.

Ok going back over your issue I think that this is due to some confusion over what's happening, not helped by the double use of the name rich_click. The first screenshot shows available imports, the second shows available imported attributes.

So, in your second screenshot, you have imported rich_click but not rich_click.rich_click. This submodule is not imported by the main package, which is why it isn't suggesting stuff under it - those things are not yet available. The suggestions show the methods available in the top-level rich_click, not available submodule imports.

If I import rich_click.rich_click instead of just rich_click then the autosuggestions work fine:

Does this make sense? Apologies for the confusing naming. I did it this way because most people will be doing import rich_click as click. Then accessing click.rich_click makes sense..

[taranlu-houzz]

@ewels Ah, haha, my bad. In hindsight, that makes sense. Thanks for pointing that out!

[ewels]

No worries! Thanks for reporting, I suspect you won't be the only person coming across this..