Remove unnecessary FieldDoesNotExistException handling
Previously, FieldDoesNotExistException was caught when extracting a field to determine whether or not it is missing (absent or an empty collection). The handling is redundant due to an earlier call to hasField so this commit removes it. Closes gh-525
This commit is contained in:
committed by
Andy Wilkinson
parent
02e842dc89
commit
5ace000c75
@@ -84,15 +84,10 @@ class JsonContentHandler implements ContentHandler {
|
||||
if (!this.fieldProcessor.hasField(candidate.getPath(), payload)) {
|
||||
return true;
|
||||
}
|
||||
try {
|
||||
ExtractedField extracted = this.fieldProcessor.extract(candidate.getPath(),
|
||||
payload);
|
||||
return extracted.getValue() instanceof Collection
|
||||
&& ((Collection<?>) extracted.getValue()).isEmpty();
|
||||
}
|
||||
catch (FieldDoesNotExistException ex) {
|
||||
return true;
|
||||
}
|
||||
ExtractedField extracted = this.fieldProcessor.extract(candidate.getPath(),
|
||||
payload);
|
||||
return extracted.getValue() instanceof Collection
|
||||
&& ((Collection<?>) extracted.getValue()).isEmpty();
|
||||
}
|
||||
|
||||
@Override
|
||||
|
||||
Reference in New Issue
Block a user