-
Notifications
You must be signed in to change notification settings - Fork 668
fix: catch invalid type used to initialize RESTObject #1487
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: catch invalid type used to initialize RESTObject #1487
Conversation
JohnVillalovos
commented
May 31, 2021
•
edited
Loading
edited
Interested to get some feedback on this. Not sure if that is the correct exception to use. |
Codecov Report
@@ Coverage Diff @@
## master #1487 +/- ##
=======================================
Coverage 91.04% 91.05%
=======================================
Files 74 74
Lines 4145 4148 +3
=======================================
+ Hits 3774 3777 +3
Misses 371 371
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Is the original idea behind this due to the malformed/unexpected response we got in the 301/302 redirect issue with POST? What exactly was the traceback there? :) |
Yes. When the
Like in #1477
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, thanks! Just a small thought from my side.
Sometimes we have errors where we don't get a dictionary passed to RESTObject.__init__() method. This breaks things but in confusing ways. Check in the __init__() method and raise an exception if it occurs.