Clarify handling of date-time offsets #1597
Merged
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
syall
approved these changes
Jan 28, 2023
gosar
approved these changes
Jan 28, 2023
srchase
force-pushed
the
clarify-datetime-offset-parsing
branch
from
5d459e2 to
297c2c7
Compare
Added in 297c2c7. |
gosar
approved these changes
Jan 30, 2023
srchase
force-pushed
the
clarify-datetime-offset-parsing
branch
from
297c2c7 to
9ebbb0e
Compare
srchase
force-pushed
the
clarify-datetime-offset-parsing
branch
from
9ebbb0e to
94bfa9b
Compare
srchase
changed the title
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.
This PR clarifies the
timestampFormattrait documentation concerning UTC offsets.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.