Closed ff137 closed 1 month ago
Confirmed that now the lint workflow (format check) fails with faulty line: https://github.com/hyperledger/aries-cloudagent-python/actions/runs/10402565667/job/28807290328?pr=3166
Thanks! I think this formatting is cleaner. I don't think it's necessary to squeeze into v1.0.0 but will approve and merge shortly.
Can confirm lint workflow also fails if lint rules are broken: https://github.com/hyperledger/aries-cloudagent-python/actions/runs/10407635261/job/28823337736?pr=3166
Failed conditions
76.8% Coverage on New Code (required ≥ 80%)
6.6% Duplication on New Code (required ≤ 3%)
It sounded like a 1.0.0 release is imminent. Is there any reason not to include format changes? 😄
It is imminent :smile: I do think this is safe enough to include. I'm going to merge and let @swcurran decide on whether to include it in the tagged release.
I'm also having linting issues with the current main branch using black, we need to make sure the tests pick this up. We had occurrences in the past where a black version upgrade introduced a significant amount of changes. This might be related to the recent black version released august 4th which bumped the version from 24.4 to 24.8.
@PatStLouis we don't have black as a formatter for acapy anymore. You should be using ruff instead.
Oh that explains a lot, missed that one. I just switched and it works pretty good! Thanks for the heads up.
Just upgrades the ruff pre-commit hook, and applies the
pre-commit run --all-files
command, as introduced in #3080edit: also fixes the lint workflow to do a formatting check
Because, when I just ran ruff format, it rekt my uncommitted work. :smile: (Now I can run format without 328 files changed)