Skip to content
New issue

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

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

Already on GitHub? # to your account

added support for empty data response #58

Merged
merged 2 commits into from
Sep 17, 2022

Conversation

Pomanks
Copy link
Contributor

@Pomanks Pomanks commented Sep 14, 2022

added OptionalDecoding protocol to support returning nil in case of empty data in response

added OptionalDecoding protocol to support returning nil in case of empty data in response
@kean
Copy link
Owner

kean commented Sep 14, 2022

This looks good, @Pomanks. I'm happy that this use case will now be supported without introducing any new public APIs.

I would appreciate if you could add a couple of tests, but that's not strictly required. I can merge it as is and add them later prior to the release.

@Pomanks
Copy link
Contributor Author

Pomanks commented Sep 15, 2022

Sure thing! I'd rather make sure the implementation was good to go before adding some.
I'll push another commit for the tests.

@kean kean merged commit 67f8cfb into kean:main Sep 17, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants