Skip to content

Fix Blazor nested validation test#67680

Merged
oroztocil merged 1 commit into
mainfrom
oroztocil/fix-tests-using-validatable-type
Jul 8, 2026
Merged

Fix Blazor nested validation test#67680
oroztocil merged 1 commit into
mainfrom
oroztocil/fix-tests-using-validatable-type

Conversation

@oroztocil

@oroztocil oroztocil commented Jul 8, 2026

Copy link
Copy Markdown
Member

This change is needed to make the nested form validation test work after #67636 before the matching SDK change is merged and flows into dotnet/aspnetcore. (Although it should not be needed afterwards, it is harmless to keep around.)

Copilot AI review requested due to automatic review settings July 8, 2026 16:33
@oroztocil oroztocil requested a review from a team as a code owner July 8, 2026 16:33
@oroztocil

Copy link
Copy Markdown
Member Author

cc @Youssef1313

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Blazor test asset model to explicitly reference the framework Microsoft.Extensions.Validation.ValidatableTypeAttribute, keeping the nested validation test working after the generator change in #67636 (until the corresponding SDK change flows in).

Changes:

  • Replace [ValidatableType] with [Microsoft.Extensions.Validation.ValidatableType] on OrderModel to avoid relying on an unqualified attribute name.

@oroztocil oroztocil enabled auto-merge (squash) July 8, 2026 16:42
@oroztocil oroztocil merged commit 0c3e825 into main Jul 8, 2026
28 checks passed
@oroztocil oroztocil deleted the oroztocil/fix-tests-using-validatable-type branch July 8, 2026 19:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants