Use DateTimeOffset everywhere instead of string
#525
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
|
👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with |
1 task
JamieMagee
force-pushed
the
datetimeoffset-everywhere
branch
from
b043b7e
to
21cfc0d
Compare
kfcampbell
approved these changes
Jul 2, 2024
There was a problem hiding this comment.
@JamieMagee I think this is a good step, thank you! I'll leave it to your discretion when to merge/how to release this.
JamieMagee
added
the
Type: Breaking change
|
Hey @JamieMagee, anything blocking this PR? |
|
@ilmax I cut this as v3.0.0 |
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.
Resolves #524
Before the change?
stringandDateTimeOffsetfor*_atfields.After the change?
DateTimeOffseteverywhere instead ofstringPull request checklist
Does this introduce a breaking change?
Please see our docs on breaking changes to help!