-
Notifications
You must be signed in to change notification settings - Fork 77
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
Header definitions are overriding others #893
Comments
Hi @hirth-abi, The alternative would be to auto-generated a schemaName, like |
Yes, that works if the schema is different and defining the schema name in a meaningful non-generated way seems to be better 👍 (it just looks a bit strange - although technically correct - to have a different header schema per message, just because the same standardized header is sent with a different value) |
…ringwolfGH-893 Co-authored-by: Timon Back <timonback@users.noreply.github.com>
…ringwolfGH-893 Co-authored-by: Timon Back <timonback@users.noreply.github.com>
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! |
The change is available in the latest release. 🎉 Thank you for the report/contribution and making Springwolf better! |
Describe the bug
When multiple
@AsyncOperation
s with@Headers
are defined, only one of them will be used for all.Se my reproducer project where different header values should be shown:
Additionally in the old UI a strange schema with "undefined-title" is shown for it:
Dependencies and versions used
Tested in 1.5.0
Code example
master...hirth-abi:springwolf-core:header-override
Stack trace and error logs
The text was updated successfully, but these errors were encountered: