Fix recursive type model binding issue in Blazor SSR forms #63163
+285
−0
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.
Fixed a critical bug in form binding where models with recursive properties would fail to bind correctly in Blazor SSR applications.
Problem
When using
[SupplyParameterFromForm]
with models containing recursive properties, the entire model would be null instead of being properly bound:Root Cause
In
HttpContextFormValueMapper.Map()
, whenCanMap()
returned false, the method would setcontext.SetResult(null)
but continue execution instead of returning early. This caused the deserializer to run anyway, potentially overwriting the null result and leading to unpredictable behavior.Solution
Added the missing
return
statement to ensure the method exits early whenCanMap()
returns false:Testing
This fix ensures that form binding with recursive types works as expected in Blazor SSR applications.
Fixes #61341.
💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.