feat(cli): add support for TIMING env var#535
Conversation
| crossbeam-channel = { version = "0.5.8" } | ||
| dashmap = { version = "5.4.0" } | ||
| flate2 = { version = "1.0.26" } | ||
| glob = { version = "0.3.1" } |
There was a problem hiding this comment.
I have no idea why these were removed 🤔
Codecov Report
@@ Coverage Diff @@
## main #535 +/- ##
==========================================
+ Coverage 89.26% 89.67% +0.41%
==========================================
Files 154 181 +27
Lines 29760 35084 +5324
==========================================
+ Hits 26566 31463 +4897
- Misses 3194 3621 +427
... and 3 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Benchmark ResultsLinuxWindows |
4e1e3b1 to
fa6d331
Compare
fa6d331 to
bf229bf
Compare
|
|
|
@shannonrothe Please take a look. Output: |
bf229bf to
92631cf
Compare
shannonrothe
left a comment
There was a problem hiding this comment.
Looks good (I can't approve it) 🚀
Do you think it's worth determining max width of each column so the output is properly aligned?
I'll bike shed a bit later 😄 |
|
By passing CLA because this PR was submitted before the org move. |
Implements support for the
TIMINGenvironment variable in the linter/CLI. SettingTIMING=1orTIMING=truebefore running the linter (via CLI) will record the time each rule takes as a whole across all files and print the result in a table after linting is complete.