outline view - differentiate between imports and objects declared within module itself

[zachvalenta]

Thinking it'd be nice for the Outline view if we could differentiate between classes imported into a module vs. declared within, especially for the purpose of filtering by type.

I realize these are both just objects available with the namespace of a module at the language level, but from the POV of glancing at the Outline view and visually parsing, be nice if import os and from flask import Flask were represented the same way.

---

classes imported into module

classes declared with module

[zachvalenta]

Same goes for functions.

If, for example, I wanted to only see my user-defined functions in the module from the first screenshot, I don't think I can currently do it:

    "outline.showClasses": false,
    "outline.showFunctions": true,
    "outline.showModules": false,
    "outline.showVariables": false,

results in the same intermingling of imports and module-defined functions:

[karthiknadig]

This looks like it is using jedi. Can you confirm from your settings? look for jediEnabled. If it is jedi then you will have to report it here: https://github.com/davidhalter/jedi . It is a external library that we depend on.

Switching to Language Server might not address this issue. See for more details https://github.com/microsoft/python-language-server/issues/612

[brettcannon]

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on then we will be happy to re-open this issue to pick up where we left off.

[zachvalenta]

This looks like it is using jedi. Can you confirm from your settings? look for jediEnabled. If it is jedi then you will have to report it here: https://github.com/davidhalter/jedi . It is a external library that we depend on.

I'm not using jedi, at least as far as I can tell https://raw.githubusercontent.com/zachvalenta/dotfiles/master/settings.json

[zachvalenta]

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on then we will be happy to re-open this issue to pick up where we left off.

Sorry for the lag, responded to @karrtikr re: jedi usage