-
Notifications
You must be signed in to change notification settings - Fork 80
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
Schema introspection of Map<String,Foo> #838
Comments
Hi @nschwalbe, thank you for the report. We indeed did not cover maps in the current implementation, but this will be added in #839 |
The change is staged for release and will be part of the next release. If you want to try and verify it in your application today, Thank you for the report/contribution! |
Hi @timonback, thanks for your quick response! I got following exception:
|
Thanks for the update @nschwalbe We tend to err on the side of what is possible and tend to be more restrictive. Since you provided this example, we can add it to our test suite and fill the gaps of possible combinations of payloads :) I created #841, but will have @sam0r040 to have a look at it to confirm that the original restriction for xml generation is still required. |
Hi @nschwalbe Can you verify the new Snapshot that will be available in the next 10 minutes? |
@timonback Yes, it works! 👍 |
The change is available in the latest release. 🎉 Thank you for the report/contribution and making Springwolf better! |
Describe the bug
It seems that a map key and value is not introspected.
In the UI schema is object and not Foo and no examples are shown.
Dependencies and versions used
springwolf amqp 1.4.0
Code example
Renders to Example Message:
{ "map": { } }
Am I missing something? I tried Schema with additionalProperties but that didn't change anything.
List<Foo>
works, so I expected thatMap<String,Foo>
should also work.The text was updated successfully, but these errors were encountered: