Add test for nullSafeValue with mapper transformation #43441
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
spring-projects-issues
added
the
status: waiting-for-triage
philwebb
added
type: task
philwebb
pushed a commit
that referenced
this pull request
Dec 11, 2024
philwebb
added a commit
that referenced
this pull request
Dec 11, 2024
|
Thanks very much @minwoo1999! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I’ve added a test case for the newly introduced nullSafeValue method that accepts a mapper function (introduced in #42972, see #42956 for background). This test ensures the method correctly transforms the value using the provided mapper function, validating its behavior. Thank you for considering and addressing the use case!
If there are any improvements or additional suggestions, I’d greatly appreciate your feedback.