You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The dayjs function itself (except Dayjs type in case dayjs() call works properly) and utc plugin and customParseFormat, does not work as expected. It fails to handle certain input types correctly. A demo showcasing the issue can be found here.
Expected behavior
The customParseFormat plugin should handle Dayjs, Date, and number input types correctly, just as it does for string types.
Information
Day.js Version: v1.11.13
OS: Fedora 6.10.12-100.fc39.x86_64
Browser: Chrome Version 129.0.6668.89 (Official Build) (64-bit)
Time zone: Berlin (GMT+2)
The text was updated successfully, but these errors were encountered:
av-k
added a commit
to av-k/dayjs
that referenced
this issue
Oct 9, 2024
Describe the bug
The
dayjs
function itself (exceptDayjs
type in casedayjs()
call works properly) andutc
plugin andcustomParseFormat
, does not work as expected. It fails to handle certain input types correctly. A demo showcasing the issue can be found here.Expected behavior
The
customParseFormat
plugin should handleDayjs
,Date
, andnumber
input types correctly, just as it does forstring
types.Information
The text was updated successfully, but these errors were encountered: