Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Tolerate extra keys when deserializing HTTP response #529

Merged
merged 1 commit into from
Dec 16, 2024
Merged

Tolerate extra keys when deserializing HTTP response #529

merged 1 commit into from
Dec 16, 2024

Conversation

leoll2
Copy link
Collaborator

@leoll2 leoll2 commented Dec 16, 2024 •
edited
Loading

Changes:

  • Improve HTTP response parser to tolerate extra keys
    • the extra keys often originate from non-breaking API changes and mismatching SDK versions

@leoll2
Improve HTTP response parsing to tolerate extra keys
fcce1ff 
the extra keys often originate from non-breaking API changes and mismatching SDK versions
@leoll2 leoll2 self-assigned this Dec 16, 2024
@leoll2
Copy link
Collaborator Author

leoll2 commented Dec 16, 2024

Reviewed in #526 for release 2.6.0

@leoll2 leoll2 merged commit 0f0e573 into main Dec 16, 2024
12 checks passed
@leoll2 leoll2 deleted the leo/handle-non-breaking-api-changes-main branch December 16, 2024 12:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@yvolokitin yvolokitin yvolokitin approved these changes

Assignees

@leoll2 leoll2

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@leoll2 @yvolokitin