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

Fix for empty grain response deseriaslized to null #2027

Merged
merged 1 commit into from
Jul 2, 2023
Merged

Fix for empty grain response deseriaslized to null #2027

merged 1 commit into from
Jul 2, 2023

Conversation

Ivanvv
Copy link
Contributor

@Ivanvv Ivanvv commented Jul 1, 2023

Description

Bug: when a grain responses with empty class or class containing all default data, it will be deserialized to 'null' on the receiving end.
After fix - it will be deserialized to empty class

Purpose

This pull request is a:

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

…) deseriaslized to null response on receiving end
@CLAassistant
Copy link

CLAassistant commented Jul 1, 2023

CLA assistant check
All committers have signed the CLA.

@rogeralsing rogeralsing merged commit 1230a66 into asynkron:dev Jul 2, 2023
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