The linter currently set for the project, is not linting what should be linted (software directory).
Furthermore, as discussed in this PR, the linter isn't black as advertised, but ruff, leading to confusion.
Solution
Add actual software directory to the list in the pre-commit black (instead of ruff) config.
Tested on
[x] macOS
[x] Windows
[ ] Ubuntu
Discussion
Re-opened after it was accidentally closed by Git after a rebase.
@tyfiero again, the fate of this PR is tied to however you choose to proceed with #213 and the ruff vs black
@tyfiero this is updated and ready for another review.
This PR, albeit necessary for smoother collaboration, generates a lot of diff in many files—the actual linting.
Therefore, it has been broken into two distinct commits. This will facilitate review (only the first commit is actually proceeding with fixing the pre-commit issue) and should help any regression investigation via git bisect, if ever needed.
Tests from the Tested on section also include actually running the CLI simulator to ensure there were no regression.
Closes #208.
Problem
The linter currently set for the project, is not linting what should be linted (
software
directory).Furthermore, as discussed in this PR, the linter isn't
black
as advertised, butruff
, leading to confusion.Solution
Add actual
software
directory to the list in the pre-commitblack
(instead ofruff
) config.Tested on
Discussion
Re-opened after it was accidentally closed by Git after a rebase.
@tyfiero again, the fate of this PR is tied to however you choose to proceed with #213 and the@tyfiero this is updated and ready for another review.ruff
vsblack
This PR, albeit necessary for smoother collaboration, generates a lot of diff in many files—the actual linting. Therefore, it has been broken into two distinct commits. This will facilitate review (only the first commit is actually proceeding with fixing the pre-commit issue) and should help any regression investigation via
git bisect
, if ever needed.Tests from the Tested on section also include actually running the CLI simulator to ensure there were no regression.