You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 14, 2018. It is now read-only.
In WebApi this was handled by a ignoring validation for a hand-picked set of types and ignoring thrown exceptions. Should we stick to the same list? (The list seem to have been updated whenever a user reported a specific type is throwing.) Should we adopt a better way of handling this?
One thought after discussing with @pranavkm - Should we add a [DoNotValidate] attribute which ignore validation for the particular property and its children?
The text was updated successfully, but these errors were encountered:
Fix: The MvcOptions takes in a list of ExcludeFromValidationDelegate (Func<Type,bool>). This func verifies if the type is excluded in validation or not.
In WebApi this was handled by a ignoring validation for a hand-picked set of types and ignoring thrown exceptions. Should we stick to the same list? (The list seem to have been updated whenever a user reported a specific type is throwing.) Should we adopt a better way of handling this?
One thought after discussing with @pranavkm - Should we add a [DoNotValidate] attribute which ignore validation for the particular property and its children?
The text was updated successfully, but these errors were encountered: