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.

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

Allow SDK to handle No Content (204) responses #105

Merged
merged 2 commits into from
Jul 22, 2024

Conversation

joshuaflanagan
Copy link
Contributor

Previously, the SDK would throw an exception when trying to parse an empty string.
Now we will return the empty string, if a string response is requested.

If the caller was expecting a deserialized type, an exception will still be raised for no content.

Previously, the SDK would throw an exception when trying to parse an empty string.
Now we will return the empty string, if a string response is requested.

If the caller was expecting a deserialized type, an exception will still be raised for no content.
@coveralls
Copy link

coveralls commented Jul 22, 2024

Pull Request Test Coverage Report for Build 10049703188

Details

  • 3 of 3 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.02%) to 82.821%

Totals Coverage Status
Change from base Build 9958897828: 0.02%
Covered Lines: 803
Relevant Lines: 956

💛 - Coveralls

@joshuaflanagan joshuaflanagan merged commit 827664c into main Jul 22, 2024
5 checks passed
@joshuaflanagan joshuaflanagan deleted the allow-no-content-response branch July 22, 2024 23:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants