Fix arrival timestamp format #567
Closed
Conversation
This file contains 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
ericrwolfe
reviewed
Sep 19, 2017
| @@ -226,7 +226,7 @@ | |||
| event.put(KEY_DISTANCE_COMPLETED, distanceCompleted); | |||
| event.put(KEY_DISTANCE_REMAINING, distanceRemaining); | |||
| event.put(KEY_DURATION_REMAINING, durationRemaining); | |||
| event.put(KEY_ARRIVAL_TIMESTAMP, arrivalTimestamp); | |||
| event.put(KEY_ARRIVAL_TIMESTAMP, TelemetryUtils.generateCreateDateFormatted(arrivalTimestamp)); | |||
There was a problem hiding this comment.
Per #566 (review), arrivalTimestamp may be null/uninitialized. Will this support that?
|
Fixed in #566 👀 f4925a3#diff-d170adec4bac91248ed199764e5e3ae0R280 Closing here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
arrivalTimestampformat to use ISO8601 format like the rest of the dates👀 @cammace @ericrwolfe @zugaldia