-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Fix Reactive Route stream serialization without relying on the Multi sub-type #21643
Fix Reactive Route stream serialization without relying on the Multi sub-type #21643
Conversation
This a breaking change, right? Because previously, the |
Yes, it is breaking if you were configuring ‘produces.’ However, in practice, it should not happen too much (still needs to be mentioned. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've added few minor comments..
...routes/deployment/src/main/java/io/quarkus/vertx/web/deployment/ReactiveRoutesProcessor.java
Outdated
Show resolved
Hide resolved
extensions/reactive-routes/runtime/src/main/java/io/quarkus/vertx/web/ReactiveRoutes.java
Outdated
Show resolved
Hide resolved
…not require a specific Multi sub-type. Sub-typing Multi does not work when the route is protected using @RolesAllowed as the security interceptor changes the returned Multi actual type. The previous approach is still supported but is deprecated. The documentation mentions the new approach and explains why the previous approach should be avoided.
cda9429
to
6949c56
Compare
Milestone is already set for some of the items: We haven't automatically updated the milestones for these items.
|
@cescoffier Pls add a note to the migration guide. |
Provide another way to generate streams from Reactive Routes that do not require a specific Multi sub-type.
Sub-typing Multi does not work when the route is protected using @RolesAllowed as the security interceptor changes the returned Multi actual type.
The previous approach is still supported but is deprecated. The documentation mentions the new approach and explains why the previous approach should be avoided.
CC @michalszynkiewicz
Fix #21044