`isort` when run via the VSCode extension is inconsistent with the result of running `isort` separately about vscode-isort

[HarrisonWilde]

Ok, adding --known-first-party mypackage arguments to the extension settings appendage fixes this problem.

Feel free to close this issue. However, I find it odd that there would be this discrepancy as this is not required when running isort directly.

[brettcannon]

The discrepancy is quite possibly due to isort; we have discovered multiple places where isort operates differently when run against a file path compared to having code passed in via stdin (which is the default when using a language server).

We actually recommend people try our ruff as it supports isort-compatible import sorting, is extremely fast, and has a great VS Code extension: https://marketplace.visualstudio.com/items?itemName=charliermarsh.ruff .