Conversation
…eusable functions.
Also, used better naming for the tests of day-long offets.
…side the converter functions.
LswaN58
deleted the
issue/232-clean-internal-logic-for-time-conversions
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In general, we should now be able to support the following forms of timedeltas. A +/- indicates we test for both positive and negative timedeltas with given format:
Note : Based on the formats above, a string with a single colon (:) will be interpreted as clock time, i.e. hours and minutes.
For Example : 1:23 will be interpreted as one (1) hour, twenty-three (23) minutes.
Similar formats are supported for timezones (by virtue of parsing a timedelta as the offset from UTC), optionally including a UTC[+/-] as prefix.
Resolves #232
Resolves #233