Skip to content
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

Passing parent model instead of nested type to resolve exception thrown by FluentValidation #198

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

icnocop
Copy link
Contributor

@icnocop icnocop commented Oct 3, 2023

Fixes #76

@icnocop icnocop marked this pull request as draft October 3, 2023 21:55
@matthetherington
Copy link

This wouldn't work if a sub object property was changed.

Eg if a Customer has an Address, and Customer.Address.Line1 changed, then editContext.Model would be of type Customer, and it would try to validate Customer.Line1, which doesn't exist.

I've made a change in #205 that should fix the same issue, could you see if it works for your use case?

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.

[Bug] Nested Complex Type Validation Fails
2 participants