-
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
REST Client Reactive: support POJO as non-file fields in multipart messages #20127
REST Client Reactive: support POJO as non-file fields in multipart messages #20127
Conversation
/** | ||
* based on {@link io.vertx.ext.web.client.impl.MultipartFormUpload} | ||
*/ | ||
public class QuarkusMultipartFormUpload implements ReadStream<Buffer> { |
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 sure hope this is a straight copy of io.vertx.ext.web.client.impl.MultipartFormUpload
, otherwise it will be impossible to vouch for :)
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.
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.
Great!
My only real question is whether all the codepaths are tested |
The integration test we had tested all the cases but passing a POJO. |
106b744
to
3ace402
Compare
done |
Do you plan a backport to 2.2? If not, for what reason? @geoand @michalszynkiewicz |
Not really as it could introduce regressions we don't want in patch releases. |
fixes #19892