Replies: 2 comments 4 replies
-
|
I just realized there is even an |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
I am working on a v2 release of the library. A part of the v2 release is going to be a result factory rework. It is going to be possible to return a null value to the action filter to prevent the action filter from short circuiting. Besides returning null I will also expose a new parameter that will allow you to prevent the validation filter from short circuiting the request. public Task<IActionResult?> Create(MvcAutoValidationContext mvcAutoValidationContext)
{
return Task.FromResult<IActionResult?>(null);
} |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi.
I'm currently trying to implement AutoValidation for my controller methods. Validation happens as expected, but in case of a validation error the Controller-Action is never called as the pipeline gets aborted before.
I'd like to keep our current logic which looks something like this:
I think this could be handled by another configuration setting that defines to still continue running the pipeline even if a validation error occurs. Maybe I'm also overlooking some other possibility to reach my goal.
Any thoughts on this?
Beta Was this translation helpful? Give feedback.
All reactions