Skip to content

Conversation

christophstrobl
Copy link
Member

This PR fixes a regression that prevented user provided custom converters from taking precedence over framework defined ones.

Resolves: #5036

This commit fixes a regression that prevented user provided custom converters from taking precedence over framework defined ones.
@@ -378,7 +378,7 @@ ConverterConfiguration createConverterConfiguration() {

if (!useNativeDriverJavaTimeCodecs) {

converters.addAll(customConverters);
converters.addAll(0, customConverters); // need to add at index 0!!
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, shouldn't converters go into STORE_CONVERSIONS?

@christophstrobl christophstrobl deleted the issue/4.5.x/5036 branch September 9, 2025 12:00
@mp911de mp911de added this to the 4.4.10 (2024.1.10) milestone Sep 9, 2025
@mp911de mp911de linked an issue Sep 9, 2025 that may be closed by this pull request
@mp911de mp911de added type: bug A general bug type: regression A regression from a previous release and removed type: bug A general bug labels Sep 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: regression A regression from a previous release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Default behavior for BigDecimal changed and broke custom converters
2 participants