From 30c51ab5ace3f1182b154886e00e508533b0950c Mon Sep 17 00:00:00 2001 From: Pedro Igor Date: Fri, 6 Jan 2023 10:43:35 -0300 Subject: [PATCH] MultiPartConfig in HTTP Vert.x extension is insufficiently documented Closes quarkusio#30046 Co-authored-by: Guillaume Smet --- .../io/quarkus/vertx/http/runtime/MultiPartConfig.java | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/extensions/vertx-http/runtime/src/main/java/io/quarkus/vertx/http/runtime/MultiPartConfig.java b/extensions/vertx-http/runtime/src/main/java/io/quarkus/vertx/http/runtime/MultiPartConfig.java index a0e262b28d6e5..43cfe26f7ed3a 100644 --- a/extensions/vertx-http/runtime/src/main/java/io/quarkus/vertx/http/runtime/MultiPartConfig.java +++ b/extensions/vertx-http/runtime/src/main/java/io/quarkus/vertx/http/runtime/MultiPartConfig.java @@ -15,7 +15,12 @@ public class MultiPartConfig { /** - * A list of {@code ContentType} to indicate whether a given multipart field should be handled as a file part. + * A comma-separated list of {@code ContentType} to indicate whether a given multipart field should be handled as a file + * part. + * + * You can use this setting to force HTTP-based extensions to parse a message part as a file based on its content type. + * + * For now, this setting only works when using RESTEasy Reactive. */ @ConfigItem @ConvertWith(TrimmedStringConverter.class)