Fixed old StrictNullChecks
to throw exceptions similar to those thrown by new StrictNullChecks
#1020
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.
To deprecate the old
StrictNullChecks
option, changes were made to make the exceptions thrown by the old process the similar to the newStrictNullChecks
.This means that the old
StrictNullChecks
will no longer throwMissingKotlinParameterException
.In the situation where this error occurs, it was inappropriate to use
MissingKotlinParameterException
because the input was not missing.This is also relevant for #617.
The following is a comparison of the respective messages displayed when
printStackTrace
is performed on the result ofassertThrows
forcom.fasterxml.jackson.module.kotlin.test.StrictNullChecksTest
(NewStrictNullChecks) andStrictNullChecksTestOld
.As for messages, it has been improved so that even the key of a value that was
null
can be checked.ClassWithArrayOfInt
NewStrictNullChecks
Fixed old
StrictNullChecks
Conventional old
StrictNullChecks
ClassWithListOfInt
NewStrictNullChecks
Fixed old
StrictNullChecks
Conventional old
StrictNullChecks
ClassWithMapOfStringToInt
NewStrictNullChecks
Fixed old
StrictNullChecks
Conventional old
StrictNullChecks