Skip to content
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

Better error messages on failing to parse a server response #25

Open
craigcitro opened this issue May 13, 2015 · 0 comments
Open

Better error messages on failing to parse a server response #25

craigcitro opened this issue May 13, 2015 · 0 comments

Comments

@craigcitro
Copy link
Contributor

Currently, failing to parse a response as the appropriate type from the server leads to somewhat incomprehensible error messages (usually related to type mismatches between a dict and a str).

Instead, we should provide something clearer, along the lines of Could not parse response "{...}" as object of type <typename>.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant