Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider null value settings for types with custom conversion. #4728

Draft
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

christophstrobl
Copy link
Member

This PR fixes an issue where settings regarding storage of null values had been ignored if a custom converter took care of the conversion.

Let's do an initial round of review and check how dbrefs should be treated when there's this kind of conversion. Also, if we decide to go for it, we need to update the documentation.

This commit fixes an issue where settings regarding storage of null values had been ignored if a custom converter took care of the conversion.
return this;
}

return new DocumentAccessor(this.document) {
Copy link
Member

Choose a reason for hiding this comment

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

If we want to handle field write checks here, how about creating a named subclass that we would use across MappingMongoConverter in the write paths?

@CybAtax
Copy link

CybAtax commented Jul 17, 2024

Hey guys, this PR looks like it would greatly fix the issue we'd have with the recent spring boot version. I was wondering, whether any update to this is planned? If support for this issue is desired, I'd love to help :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Null-Values from custom converters are stored in document
3 participants