-
Notifications
You must be signed in to change notification settings - Fork 44
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
Outdated de-serialization of topic response #80
Comments
Same problem as with this issue #69 . |
I got the impression that the whole SDK is heavily outdated. I found more and more situations where it was firing wrong requests. Additionally, it's often enough hiding errors (esp. HTTP errors) and failure reports from responses. I guess one shouldn't really use it atm. |
When I run a request for a topic, the response is not deserialized properly. This is b/c the received JSON looks like this:
, but the
struct
GetTopicResponse
doesn't expectdata
but the inner item:I can imagine this also applies to other requests I did not stumble upon. I could create a PR for
GetTopicResponse
, but I'm not sure whether that's the way to go or whether you're generating your SDKs from another place. :)The text was updated successfully, but these errors were encountered: