JdbcCustomConversion does not reject non-Date related default converters anymore #937
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.
Previously,
JdbcCustomConversion
rejected any default converter that was not converting from and tojava.util.Date
. This probably stemmed from the fact that up until recently, Spring Data Commons'CustomConversions
only registered date related default converters. As of spring-projects/spring-data-commons#2315 we also support jMolecules'Association
andIdentifier
converters. We've relaxed the rejection to only explicitly reject all non Date/Time related converters if the conversion is from/tojava.util.Date
but allow everything else out of the box.