Rename formatter_progress to formatter_ecosystem_checks (#6194)

Rename the `scripts/formatter_progress.sh` to
`formatter/formatter_ecosysytem_checks.sh` since it fits the actual task
better.
This commit is contained in:
konsti 2023-07-31 20:33:12 +02:00 committed by GitHub
parent e52b636da0
commit a7aa3caaae
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 8 additions and 7 deletions

View file

@ -231,12 +231,13 @@ additional test cases in `resources/test/fixtures/ruff`.
The full Ruff test suite is slow, `cargo test -p ruff_python_formatter` is a lot faster.
You can check the black compatibility on a number of projects using `scripts/formatter_progress`.
It will print the similarity index, the percentage of lines that remains unchanged between black's
formatting and our formatting. You could compute it as the number of neutral lines in a diff divided
by the neutral plus the removed lines. It also checks for common problems such unstable formatting,
internal formatter errors and printing invalid syntax. We run this script in CI and you can view the
results in a PR page under "Checks" > "CI" > "Summary" at the bottom of the page.
You can check the black compatibility on a number of projects using
`scripts/formatter_ecosystem_checks.sh`. It will print the similarity index, the percentage of lines
that remains unchanged between black's formatting and our formatting. You could compute it as the
number of neutral lines in a diff divided by the neutral plus the removed lines. It also checks for
common problems such unstable formatting, internal formatter errors and printing invalid syntax. We
run this script in CI and you can view the results in a PR page under "Checks" > "CI" > "Summary" at
the bottom of the page.
There is a `ruff_python_formatter` binary that avoid building and linking the main `ruff` crate.