I just tested Black and its usage in Atom using your plugin and I found something really weird. Attached you'll find the zip-file controller_test_black.zip, which contains three files. The first one is the original file, almost ready formatted, but slightly changed it for testing purposes. Using black from command line results in the file with "_2" as suffix. This is what I expect. But using it from within Atom using python-black results in file "_3". You'll see that the file is completely screwed up.
Switching back in Atom using CMD+z brinks back only parts of it. Fortunately I can checkout my file again from my GIT repository.
I honestly do not have any clue why Black behaves completely different from within Atom/python-black and from command line. atom-beautify works like expected.
Regards, Thomas
EDIT: I tried Black using a similar plugin - works like expected.
Hi,
I just tested Black and its usage in Atom using your plugin and I found something really weird. Attached you'll find the zip-file controller_test_black.zip, which contains three files. The first one is the original file, almost ready formatted, but slightly changed it for testing purposes. Using black from command line results in the file with "_2" as suffix. This is what I expect. But using it from within Atom using python-black results in file "_3". You'll see that the file is completely screwed up.
Switching back in Atom using CMD+z brinks back only parts of it. Fortunately I can checkout my file again from my GIT repository.
I honestly do not have any clue why Black behaves completely different from within Atom/python-black and from command line. atom-beautify works like expected.
Regards, Thomas
EDIT: I tried Black using a similar plugin - works like expected.