Actual Behaviour
Currently, we are manually parsing dates in various sections of app, where some ignore timezone and some use another mechanism to parse it.
Expected Behaviour
For an event-based application, it is trivial to do correct and standard date conversions so it must happen in a single tested class which correctly handles all edge cases and TZ information correctly
Would you like to work on the issue?
Yes, but if anyone else is interested, he/she may take it up
@arp95 The current date handling is very erroneous and repetitive. I am rewriting the date class, so you can hold the test writing for now. Sorry for the inconvenience
@iamareebjamal can i work on that? i actually made changes so would like to work on that.
Definitely. Thank you
Please share the proposed API before writing the code here and is Milestone 4 OK?
yeah its fine.
will share the functions i am using and then will submit the pr. is it fine?
Yes :+1:

@iamareebjamal should i make any changes?
No, it's great :+1:
Most helpful comment
@iamareebjamal should i make any changes?