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
In some cases (like filter property in DatePicker component) a Dayjs instance is provided for end-users for dates filtering. It leads to the following problems:
Necessity to learn a new syntax, even though the project may not use Day.js. For example, we use date-fns, which works with the native Date objects
It exposes the implementation details. Each time the implementation (approach/library to work with dates) changes, it will be a breaking change for end-users
To Do
Expose Date instead of Dayjs instance in all places end-users can use it. Since Dayjs is an implementation detail, which I talked about above, right now it will be a breaking change
The text was updated successfully, but these errors were encountered:
Now
In some cases (like
filter
property inDatePicker
component) aDayjs
instance is provided for end-users for dates filtering. It leads to the following problems:Day.js
. For example, we use date-fns, which works with the nativeDate
objectsTo Do
Date
instead ofDayjs
instance in all places end-users can use it. SinceDayjs
is an implementation detail, which I talked about above, right now it will be a breaking changeThe text was updated successfully, but these errors were encountered: