Treat Kotlin nullable as non-required
Where `isOptional` is used, also check for `isNullable` i.e. values are not considered required if they are Kotlin nullables: - spring-messaging: named value method arguments - spring-web: named value method arguments - spring-webmvc: request parts This means that Kotlin client code no longer has to explicity specify "required=false" for Kotlin nullables -- this information is inferred automatically by the framework. Issue: SPR-14165
This commit is contained in:
committed by
Sebastien Deleuze
parent
735e288d46
commit
fada91e538
@@ -113,7 +113,8 @@ public class RequestPartMethodArgumentResolver extends AbstractMessageConverterM
|
||||
|
||||
HttpServletRequest servletRequest = request.getNativeRequest(HttpServletRequest.class);
|
||||
RequestPart requestPart = parameter.getParameterAnnotation(RequestPart.class);
|
||||
boolean isRequired = ((requestPart == null || requestPart.required()) && !parameter.isOptional());
|
||||
boolean isRequired = ((requestPart == null || requestPart.required()) && !parameter.isOptional() &&
|
||||
!parameter.isNullable());
|
||||
|
||||
String name = getPartName(parameter, requestPart);
|
||||
parameter = parameter.nestedIfOptional();
|
||||
|
||||
Reference in New Issue
Block a user