test: [OpenAPI-Gen] Deserialising oneOf and anyOf with array of objects
#752
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
newtork
approved these changes
Mar 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
AI/ai-sdk-java-backlog#681.
We aim to test if the proposed OpenAPI spec definition may hinder Java SDK development.
Specifically, the specification contains properties that may be
oneOftypes, including both primitive and complex types. The tests are designed to verify the deserialization for bothoneOfandanyOfscenarios.Note: The spec doesn't contain
anyOfcase yet.Definition of Done
Error handling created / updated & covered by the tests aboveDocumentation updatedRelease notes updated