-
Notifications
You must be signed in to change notification settings - Fork 3
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
[PropertyMappingPopulator] Make null safety possible #68
Comments
What's the problem with reading |
The reading of null values is no problem but sometimes you don't want to set in case of a null value. |
We have in our project context the following situation:
You can not use the PropertyMappingPopulator here. Otherwise you would set target properties to null. |
mike4git
added a commit
that referenced
this issue
Mar 18, 2024
…pulator add test for dot operator add debug functionality to php docker container for testing
mike4git
added a commit
that referenced
this issue
Mar 18, 2024
mike4git
added a commit
that referenced
this issue
Mar 18, 2024
mike4git
added a commit
that referenced
this issue
Mar 20, 2024
mike4git
added a commit
that referenced
this issue
Apr 2, 2024
…pulator add test for dot operator add debug functionality to php docker container for testing
mike4git
added a commit
that referenced
this issue
Apr 2, 2024
mike4git
added a commit
that referenced
this issue
Apr 2, 2024
mike4git
added a commit
that referenced
this issue
Apr 2, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
PropertyMappingPopulator
should be able to be configured that in case the source property value is null either accessor should be called or accessor should not be called (null safety).Therefore it is recommended, that a new property
$nullSafety
of typebool
will be introduced called nullSafety (by default: false - cause this is the current default behaviour).The text was updated successfully, but these errors were encountered: