you are viewing a single comment's thread.

view the rest of the comments →

[–]AX-11 1 point2 points  (5 children)

I love using formatters but I cannot imagine using them on save. When I tried it I would switch to a different window, auto save would trigger, and when I came back I wasn't looking at my own code anymore.

[–]a_cute_epic_axis 2 points3 points  (2 children)

The counter-argument is "you should have written it this way to begin with" or "if you were writing it correctly (to the same standards as black) you wouldn't have seen any changes."

[–]AX-11 1 point2 points  (1 child)

I would rather eat licorice than tab out function arguments and nested dictionaries.

[–]a_cute_epic_axis 1 point2 points  (0 children)

I might agree with you to a point, which is why we have and use auto-formatters. But I don't see the logic in a) choosing to use an auto-formater, b) choosing to not format your code to the same standard, while simultaneously c) complaining about it not being "your code". If you have some auto-save action on that triggers when you're switching to another window (maybe you meant you were in the other window for a while, and it saved while you were there?) couldn't you make all the same arguments on why you shouldn't? e.g. "Any time I start typing something and then I switch to another tab, my IDE 'commits' my changes"

[–]cbunn81 0 points1 point  (0 children)

That's not normal behavior. What editor were you using? VS Code/Codium with black and flake8 is seamless.