Resolve property-dependent parameter names for exception messages
Prior to this commit when a required parameter defined as a property or expression placeholder was missing, the exception thrown would refer to the placeholder instead of the resolved name. This change covers messaging handlers and web controllers, both blocking and reactive. It also fixes the error message when handling null values for non-required parameters, as well as in cases that need conversion. See gh-32323 Closes gh-32462
This commit is contained in:
committed by
Simon Baslé
parent
5698191ba0
commit
458c30cb63
@@ -123,10 +123,10 @@ public abstract class AbstractNamedValueMethodArgumentResolver implements Handle
|
||||
arg = resolveEmbeddedValuesAndExpressions(namedValueInfo.defaultValue);
|
||||
}
|
||||
else if (namedValueInfo.required && !nestedParameter.isOptional()) {
|
||||
handleMissingValue(namedValueInfo.name, nestedParameter, webRequest);
|
||||
handleMissingValue(resolvedName.toString(), nestedParameter, webRequest);
|
||||
}
|
||||
if (!hasDefaultValue) {
|
||||
arg = handleNullValue(namedValueInfo.name, arg, nestedParameter.getNestedParameterType());
|
||||
arg = handleNullValue(resolvedName.toString(), arg, nestedParameter.getNestedParameterType());
|
||||
}
|
||||
}
|
||||
else if ("".equals(arg) && namedValueInfo.defaultValue != null) {
|
||||
@@ -142,7 +142,7 @@ public abstract class AbstractNamedValueMethodArgumentResolver implements Handle
|
||||
arg = convertIfNecessary(parameter, webRequest, binderFactory, namedValueInfo, arg);
|
||||
}
|
||||
else if (namedValueInfo.required && !nestedParameter.isOptional()) {
|
||||
handleMissingValueAfterConversion(namedValueInfo.name, nestedParameter, webRequest);
|
||||
handleMissingValueAfterConversion(resolvedName.toString(), nestedParameter, webRequest);
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user