Given the scenario below where I have select 03/01/2018 22:15 UTC while my computer system is UTC+05:00, I have identified a bug with the DateTimePicker module. This is from the v1.7.0 release, however I believe 1.8.5 behaves similarly as the code has marginal variances and does not address the changes I have made ad-hoc. You can see from the image that the 1.7.0 codebase creates a local preview time of the same day which is inaccurate; it should be the following day based on the computer system time zone.
Given the scenario below where I have select 03/01/2018 22:15 UTC while my computer system is UTC+05:00, I have identified a bug with the DateTimePicker module. This is from the v1.7.0 release, however I believe 1.8.5 behaves similarly as the code has marginal variances and does not address the changes I have made ad-hoc. You can see from the image that the 1.7.0 codebase creates a local preview time of the same day which is inaccurate; it should be the following day based on the computer system time zone.
Here are the lines under question:
https://github.com/CenturyLinkCloud/Cyclops/blob/3a814e5246befb35056c87a2904222508172a3bf/src/scripts/models/DateTimePickerViewModel.coffee#L78-L90