ARTEMIS-5534 use Objects.requireNonNullElse() where sensible #5771
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The code-base is littered with uses of Java's ternary operator to check for null and fallback to a default value. Many of these can be replaced with either
Objects.requireNonNullElse
orObjects.requireNonNullElseGet
. The latter is used where appropriate to essentially match the short-circuit semantics provided by the ternary operator.