perf: avoid creating Date objects when parsing timestamps#2256
perf: avoid creating Date objects when parsing timestamps#2256ghostdevv merged 1 commit intonpmx-dev:mainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (9)
📝 WalkthroughWalkthroughThis pull request systematically replaces Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 1✅ Passed checks (1 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 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 |
🔗 Linked issue
N/A
🧭 Context
Uses
Date.parse(...)instead ofnew Date(...).getTime()when converting date strings to timestamps.📚 Description
Uses
Date.parse(...)instead ofnew Date(...).getTime()when converting date strings to timestamps. This avoids creating unnecessary Date objects while keeping the behavior the same for string-based parsing paths used in sorting, TID generation, and related tests.