-
Notifications
You must be signed in to change notification settings - Fork 58
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
Question about validation_middleware #64
Comments
@korcky, you talk about usage of |
@maximdanilchenko, yep, you're correct |
Yes. You are right. It is an issue and it is my fault. It was designed like it in the very beginning of the project. And it was incorrect to change the behavior after some time. I will remove this |
I'm not quite affected by this issue for now) So, I think it would better to fix in 2.0 version. |
Currently code of this method looks like:
So, if schema successfully parsed a request arguments (basically transform each argument to their relative type), they will be put in
result
, but eventually (ifdata
a dictionary) arguments inresult
will be replaced by their string representation.The question is
Why?
Why replacing a right type arguments with their string representation?The text was updated successfully, but these errors were encountered: