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

Improve serialization of "single-or-many" properties #8090

Merged
merged 1 commit into from Apr 5, 2024

Conversation

flobernd
Copy link
Member

@flobernd flobernd commented Apr 5, 2024

Closes #8056

Copy link
Contributor

@stevejgordon stevejgordon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The serialization changes look okay to me. It would probably be worth adding some test cases for these now we have a reasonable understanding of the nuances of the API and the expected formats of the data.

@flobernd
Copy link
Member Author

flobernd commented Apr 5, 2024

That's definitely a good idea. I'll add some tests in a following step after I updated the tests for 8.13 in general 🙂

@flobernd flobernd merged commit 5ccd393 into main Apr 5, 2024
10 of 24 checks passed
@flobernd flobernd deleted the fix-empty-single-or-many-descriptor branch April 5, 2024 13:01
flobernd added a commit that referenced this pull request Apr 5, 2024
Co-authored-by: Florian Bernd <git@flobernd.de>
flobernd added a commit that referenced this pull request Apr 5, 2024
Co-authored-by: Florian Bernd <git@flobernd.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Empty should collection is serialized improperly
2 participants