refactor: fix or suppress existing oxlint warnings#2634
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThis pull request contains three minor changes across the codebase: adding a linter suppression comment to prevent warnings on a Changes
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
| const lastDateMs = chartData.value.dates.at(-1) ?? 0 | ||
| const isAbsoluteMetric = selectedMetric.value === 'contributors' | ||
|
|
||
| // oxlint-disable-next-line oxc-no-map-spread |
There was a problem hiding this comment.
There was a problem hiding this comment.
Maybe disable the rule in the config?
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
🔗 Linked issue
N/A
🧭 Context
There are 3 oxlint warnings on main.
📚 Description
Fix or suppress them.