Stats output similar to treefmt.rs #33
No reviewers
Labels
No Label
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
2 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: numtide/treefmt#33
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "feat/stats"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Helps to understand what happened with the following stats:
traversed
is the number of files we walked overemitted
is the number of files we had no cache entry for, or for which we had a cache entry but themtime
has changedmatched
is the number of files we matched to one or more formatting pipelinesformatted
is the number of files that were actually changedIn the example below, we can see that we still emitted some files when using the cache, but none matched to a formatter, and none were subsequently formatted.
841441dfef
to04330a39fa
very nice!
I was surprised by the ordering between the match and the cache, but just because it's the other way around in the rust impl.