Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork5.7k
refactor: add and useparseDate
#1643
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
codecov-commenter commentedMar 18, 2024
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@## master #1643 +/- ##======================================= Coverage 84.07% 84.07% ======================================= Files 375 376 +1 Lines 19688 19694 +6 Branches 2913 2907 -6 =======================================+ Hits 16552 16558 +6 Misses 3136 3136 ☔ View full report in Codecov by Sentry. |
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Makes sense.
(Though probably these date-related functions should take "date" objects instead of strings in the first place to save them the (not very interesting) parsing.)
Co-authored-by: appgurueu <34514239+appgurueu@users.noreply.github.com>
Describe your change:
Aspromissed, this PR adds a function
parseDate
.Checklist:
Example:
UserProfile.js
is allowed butuserprofile.js
,Userprofile.js
,user-Profile.js
,userProfile.js
are notFixes: #{$ISSUE_NO}
.