Chore: add isort for devcontainer, pre-commit - #3367
Conversation
|
Oh damn it, looks like |
pre-commit says, 'no'. 😆 |
|
Hmm, |
|
I'm thinking that maybe the |
|
Seems like Black and isort are fighting with each other: Looking at the diff, I bet it's related to how lists of imports that are too long for one line are handled, e.g., in https://github.com/cal-itp/benefits/pull/3367/files#diff-e7d55a51289a0b1d4307eba90289f302563d66d2c05d7f6b0d74a292a8feea6c |
286c058 to
fb33e5a
Compare
configure isort to use the black profile, with some overrides from the Django profile and match our common line-length
so the massive isort commit is ignored in future git blames
fb33e5a to
98570ba
Compare
|
OK this is now ready for review. Thanks to @Scotchester for pointing out the I went ahead and ran
Read more about |
angela-tran
left a comment
There was a problem hiding this comment.
This looks good! Re-built my container, ran Benefits, tried out a git blame ✅
Closes #3245
For discussion / decision
Should we just install the tooling (the current state of the PR), and let files get modified over time as they are touched?
Or should we also run the tooling on all existing files and commit that in this PR as well?
I don't really have a preference,
isortmakes it easy to run against all current files if we wanted, but that could be a big commit. Maybe @Scotchester's suggestion on the Cal-ITP website project applies here as well?