feat: generate schema from example message #191
Merged
Conversation
This file contains 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
The generator has been implemented assuming that all message objects include a payload with properties. This is used when generating Java classes to be able to create attributes that matching the expected message properties. This causes the generator to fail with AsyncAPI documents that don't include payload properties. Some such documents will provide a sample message instead. For these documents, we can attempt to derive a schema from the sample, and use that schema to generate a usable set of properties. Signed-off-by: Dale Lane <dale.lane@uk.ibm.com>
dalelane
requested review from
AGurlhosur,
dan-r,
KieranM1999,
lewis-relph,
JEFFLUFC and
asyncapi-bot-eve
as code owners
|
|
/au |
KieranM1999
approved these changes
Mar 12, 2024
|
/rtm |
|
🎉 This PR is included in version 0.3.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
The generator has been implemented assuming that all message objects include a payload with properties. This is used when generating Java classes to be able to create attributes that matching the expected message properties.
This causes the generator to fail with AsyncAPI documents that don't include payload properties. Some such documents will provide a sample message instead. For these documents, we can attempt to derive a schema from the sample, and use that schema to generate a usable set of properties.