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
Use the Ical.Net types for representing the model but use NodaTime types for evaluation.
I.e. the Ical.Net types have been designed for and are great in representing the ICAL model while NodaTime has been designed for and is great in doing time- and time-zone based calculations, dealing with related ambiguities, etc. The approach would be to have a clean translation layer between the Ical.Net types and NodaTime and then doing the actual calculations in NodaTime.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Now that we're about to release v5, its time to start discussions about v6, starting with those things that didn't make it into v5.
I.e. the Ical.Net types have been designed for and are great in representing the ICAL model while NodaTime has been designed for and is great in doing time- and time-zone based calculations, dealing with related ambiguities, etc. The approach would be to have a clean translation layer between the Ical.Net types and NodaTime and then doing the actual calculations in NodaTime.
Beta Was this translation helpful? Give feedback.
All reactions