-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
fix response.text property #420
Conversation
-1 i do not like to use two different types for same attribute, |
Ok, I've made changes, now |
lgtm from me |
We have documented I'm -0.5 for making it @fafhrd91 if you insist on converting it to |
i am +-0 on this. i just do not like to use two different types for one attribute. |
I think having It works like implicit |
in swift it is different, you have to explicitly unwrap optional value, and again optional attribute has one type which is enum Optional. but we use two types for |
I still like keeping |
i'm fine with that. but i think this is wrong |
reverted to original PR. response.text is None if response.body is None |
Thanks, Коля |
response.text
has unexpected behavior:results in:
here tiny fix.