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

Closed
wants to merge 5 commits into 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.

@christophstrobl christophstrobl linked an issue Jun 18, 2024 that may be closed by this pull request
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 :)

christophstrobl and others added 5 commits August 28, 2024 08:25
This commit fixes an issue where settings regarding storage of null values had been ignored if a custom converter took care of the conversion.
@mp911de mp911de marked this pull request as ready for review August 28, 2024 06:59
@mp911de mp911de added the type: bug A general bug label Aug 28, 2024
@mp911de mp911de changed the title Consider null value settings for types with custom conversion. Consider null value settings for types with custom conversion Aug 28, 2024
@mp911de mp911de added this to the 4.2.10 (2023.1.10) milestone Aug 28, 2024
mp911de pushed a commit that referenced this pull request Aug 28, 2024
This commit fixes an issue where settings regarding storage of null values had been ignored if a custom converter took care of the conversion.

Original pull request: #4728
Closes #4710
mp911de added a commit that referenced this pull request Aug 28, 2024
mp911de pushed a commit that referenced this pull request Aug 28, 2024
This commit fixes an issue where settings regarding storage of null values had been ignored if a custom converter took care of the conversion.

Original pull request: #4728
Closes #4710
mp911de added a commit that referenced this pull request Aug 28, 2024
mp911de pushed a commit that referenced this pull request Aug 28, 2024
This commit fixes an issue where settings regarding storage of null values had been ignored if a custom converter took care of the conversion.

Original pull request: #4728
Closes #4710
mp911de added a commit that referenced this pull request Aug 28, 2024
mp911de added a commit that referenced this pull request Aug 28, 2024
Refine type visibility.

Original pull request: #4728
See #4710
@mp911de mp911de closed this Aug 28, 2024
@mp911de mp911de deleted the issue/4710 branch August 28, 2024 11:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug A general bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

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