Validate instances created by InstanceCreator
#2446
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.
Purpose
Follow-up for #2435 (comment) and comment below
Description
Validate that instances created by an
InstanceCreator
are notnull
, and are actually of the requested type. This hopefully makes troubleshooting for users easier than encountering aClassCastException
at a completely different place, without any indication that a faultyInstanceCreator
is the cause.As mentioned in #2435 (comment), there is currently code which relies on Java type erasure and Gson implementation details to misuse the missing checks and create unrelated instances. It has to be decided if it is acceptable to break that code.
Checklist
null
@since $next-version$
(
$next-version$
is a special placeholder which is automatically replaced during release)TestCase
)mvn clean verify javadoc:jar
passes without errors