• GBU_28@lemm.ee
      link
      fedilink
      English
      arrow-up
      8
      ·
      1 year ago

      With things like black, flake 8 and Isort I can code however I want, list/format however I want, and commit team compliant content. The dream is real

        • GBU_28@lemm.ee
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          So you can have a local, and a team config. So at time of commit the code rules your team has selected are enforced. So if I looked at my code, on GitHub, it would look as expected by the team.

          If I load it locally, it formats as I like.

          Check out the cicd stuff on PRs for github

    • RogueBanana@lemmy.zip
      link
      fedilink
      arrow-up
      3
      arrow-down
      1
      ·
      1 year ago

      Yeah but outside of that where the code is implemented or in a documentation, tabs are still easier to look through. And it does look pretty as long as there aren’t too many nested functions.

      • mexicancartel@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Even with nested functions tabs are neat.

        Does you app have too many nested functions?

        Use tab width = 2

        Do your app have too less nested functions?

        Use tab width = 8

        Is your app having average number of nested fns?

        Use tab width = 4(mostly default)

        And all theese can happen without modifying a single byte in the source file, unlike spaces!