Add TimeZones dependency for auto-converting Timestamp #50
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.
Implements #17. We now convert all Timestamp objects to ZonedDateTime
via auto-conversion (can be turned off by
convert=false
). The onepiece of awkwardness here is that it is currently assumed that with a
Vector{ZonedDateTime}
, it is assumed that each element will have thesame timezone. Probably ok in practice, but frankly it'd be nicer if
there was a
ZonedDateTime
type that could be parameterized by thetimezone itself so that could be enforced via type parameter.
Also fixes #48. cc: @oxinabox, @kcajf, @omus