Skip to content

Conversation

@JamieMagee
Copy link
Member

Resolves #595


Before the change?

  • Some datetime types were incorrectly deserialized

After the change?

  • Datetime types are correctly serialized

Pull request checklist

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been reviewed and added / updated if needed (for bug fixes / features)

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

  • Yes
  • No

@github-actions
Copy link

👋 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 Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

@JamieMagee JamieMagee merged commit a284684 into main Oct 22, 2024
9 checks passed
@JamieMagee JamieMagee deleted the jamiemagee/fix-datetime-properties branch October 22, 2024 02:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

[BUG]: DateTimeOffsetConverter doesn't parse null completed_at

3 participants