I can't speak for nberardi but I don't see that as important.
If in his example, captchaValid doesn't mean anything to the Login action, then the obvious solution is just to remove the argument.
However, from the code that he refers to, it seems to be setting it to either true or false and letting the action handle it, so it's less of a CaptchaValidation and more or a CaptchaReader or something like that. (not happy with "reader",
naming is that hardest part of computer science)
Even if that's not the case, the feature is still a great idea!. You can use it to do your own string > object deserialization, add per-action default route parameters, dependency injection. There's a wealth of opportunity here that i'm sure people will
take advantage of.
tgmdbm
Contributor
4392 Points
883 Posts
ASPInsiders
MVP
Re: BUG: Order of opperations in Action parameter validation seems wrong.
Mar 18, 2008 09:32 AM|LINK
I can't speak for nberardi but I don't see that as important.
If in his example, captchaValid doesn't mean anything to the Login action, then the obvious solution is just to remove the argument.
However, from the code that he refers to, it seems to be setting it to either true or false and letting the action handle it, so it's less of a CaptchaValidation and more or a CaptchaReader or something like that. (not happy with "reader", naming is that hardest part of computer science)
Even if that's not the case, the feature is still a great idea!. You can use it to do your own string > object deserialization, add per-action default route parameters, dependency injection. There's a wealth of opportunity here that i'm sure people will take advantage of.