Closed mthanded closed 2 years ago
This is by design. The way it works in the extension is, we take the plain string of text before the file is saved, and pass it to isort
via stdin. isort
then outputs the processed result.
If you need to use --verbose
then I recommend disabling this extension and using the task.json to setup a task that does this for you using the isort
s in-place edit.
Until there is a clear way to filter those out I don't see how we can support this when working with plain string buffers.
@karthiknadig got it. This came up when debugging the sort order issue. Thanks for the clarity. Will use the task approach if needed in the future
@mthanded Try setting isort.logLevel
to debug. We pretty much output the entire thing we do. Should help with debugging problems in the extension.
If
--verbose
is passed to isort the output of the verbose isort command ends up in the file instead of the transformed sort orderIf I choose quick fix with a file containing the below:
The sorted imports turn into
This is the isort command with --verbose