Comparing
no-multi-comp-rule
(13421a4
) withmain
(95df577
)0%
- Untouched
- 46
- Skipped
- 3
No successful run was found on main ( c8506f7) during the generation of this report, so 95df577 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report.
Benchmarks
3 total
The benchmarks below were skipped, so their baseline results are used instead. If they were deleted in your codebase, archive them to remove them from the performance reports.
Learn more about archiving benchmarks
Learn more about archiving benchmarks
formatter[binder.ts]
tasks/benchmark/benches/formatter.rs::formatter::bench_formatterSkipped
21.2 ms*
formatter[cal.com.tsx]
tasks/benchmark/benches/formatter.rs::formatter::bench_formatterSkipped
188.5 ms*
formatter[react.development.js]
tasks/benchmark/benches/formatter.rs::formatter::bench_formatterSkipped
10.7 ms*
Commits
Click on a commit to change the comparison rangeBase
main
95df577
-0.04%
refactor(linter): Use visitor pattern in no-multi-comp rule for better performance
7193952
24 days ago
by connorshea-0.04%
Simplify code further.
0f806af
24 days ago
by connorshea+0.03%
Add a few more tests to cover cases not handled in the existing test suite.
b3cf573
24 days ago
by connorshea+0.04%
Fix the failing tests I added.
5ea7445
24 days ago
by connorshea-0.04%
Fix lint warning.
acb45bc
24 days ago
by connorshea+0.02%
Add one more test, why not.
dc3d2a2
24 days ago
by connorshea-0.02%
Fix the visitor for no-multi-comp rule to avoid double counting certain cases.
f9b5d2d
24 days ago
by connorshea+0.01%
fix(linter): Address review feedback for no-multi-comp rule
13421a4
24 days ago
by connorshea