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 the current CalendarEventData model, we are using the object of DateTime to define the start and end time of an event. But while manipulating the event, we are only using hours and minutes from the DateTime so, it is getting confusing. Because Users have to provide the date information even though it's not being used.
So, one solution that we can implement is to use TimeOfDay to store the start and end times.
We can deprecate some variables, that define the time span of an event and move it to a separate model. And in the next major version, we can completely remove it.
The text was updated successfully, but these errors were encountered:
PRBaraiya
changed the title
User TimeOfDay instead of DateTime for start and end time in CalendarEventData.
Use TimeOfDay instead of DateTime for start and end time in CalendarEventData.
Nov 23, 2023
In the current
CalendarEventData
model, we are using the object ofDateTime
to define the start and end time of an event. But while manipulating the event, we are only using hours and minutes from theDateTime
so, it is getting confusing. Because Users have to provide the date information even though it's not being used.So, one solution that we can implement is to use TimeOfDay to store the start and end times.
We can deprecate some variables, that define the time span of an event and move it to a separate model. And in the next major version, we can completely remove it.
The text was updated successfully, but these errors were encountered: