Add test to validate <choose> tag's <otherwise> fallback when parameter is null #3500
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.
Summary
This PR adds a unit test to ensure that
<choose>
with<when>
conditions correctly falls back to<otherwise>
when a parameter is missing or null.Motivation
While MyBatis already appears to handle OGNL evaluation with missing parameters gracefully, there wasn't an explicit test to guarantee this behavior.
By adding this test, we can be more confident that:
name
is not provided, thewhen
condition fails safely.otherwise
clause executes as expected, producingAND status = 'ACTIVE'
.Details
ChooseWhenTest
undersubmitted.choosewhen
to verify this edge case.CreateDB.sql
for test setup.Notes
I wanted to provide a clear test case that proves
<choose>
properly falls back to<otherwise>
.This improves test coverage and helps ensure future refactoring doesn't accidentally break this logic.
Let me know if you'd like any adjustments!