-
Notifications
You must be signed in to change notification settings - Fork 1k
Increase readability and maintainability: scheduler setValue #1635
Increase readability and maintainability: scheduler setValue #1635
Conversation
@interactivellama please look into the CI fail |
Updated @swilliamset I couldn't allow the trainwreck that is |
var date = d.split('-'); | ||
var time = t.split(':'); | ||
setUtcTime: function setUtcTime(day, time, offset) { | ||
var dateArray = day.split('-'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
change variable name to dateSplit
and timeSplit
for consistency with other split results below. why not *Array
? personal preference. varnameArray[0]
feels redundant.
Unable to determine if interactivellama@2979e6067733cb986059380e84b6df56b1ea86a2is the solution or just happy coincidence. Without a more complete range of unit tests the side affects are unknown. Please provide an assessment of the effort required to improve unit tests. |
Will remove actual "bugfix" and submit the refactor part and open a new PR with the "bugfix" change. |
|
11:00pm + 2 = next day.
- setValue is now "a one screen function" - creates `_parseRecurrencePattern`, _parseStartDateTime`, `_parseTimeZone` - Re-uses `_parseStartDateTime` for timezone parsing - Removes commented out utcTime manipulation - Renamed variables to understandable things - Same functionality present, just increased readability
d2e23f8
to
aafcf7f
Compare
Like this: semiColonSplitPattern -> semiColonPatternSplit
Updated with refactor only. "Bugfix" removed. |
still need unit tests. assigning to @dwaltz. @interactivellama, please pass any knowledge to him. |
Increase readability and maintainability: scheduler setValue
So that it doesn't change from the values set via
setValue
.This means that the time offset is ignored in the
startDateTime
option.