You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As title mentions it completely ignores any nested config file, in my case setup.cfg.
Surprisingly even when switched to environment isort, or even when path set to the which isort that actually works properly from the command line.
isort --diff --resolve-all-configs components/core/app/gunicorn_app.py gives completely different output as does in VScode, using the mentioned --resolve-all-configs arg, no matter bundled, environment or path explicit is setted up.
I've an instance of setup.cfg file both in project's root folder and in components/core folder, main difference is the headings strings and a known_first_party=app setting on the one in components/core folder.
This works flawlessly on command line.
The text was updated successfully, but these errors were encountered:
As title mentions it completely ignores any nested config file, in my case
setup.cfg
.Surprisingly even when switched to environment
isort
, or even when path set to thewhich isort
that actually works properly from the command line.isort --diff --resolve-all-configs components/core/app/gunicorn_app.py
gives completely different output as does in VScode, using the mentioned--resolve-all-configs
arg, no matter bundled, environment or path explicit is setted up.I've an instance of
setup.cfg
file both in project's root folder and incomponents/core
folder, main difference is theheadings
strings and aknown_first_party=app
setting on the one incomponents/core
folder.This works flawlessly on command line.
The text was updated successfully, but these errors were encountered: