-
Notifications
You must be signed in to change notification settings - Fork 89
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
Unmarshal error ignored #209
Comments
What version of the go client library are you using? I tried using
|
Correct there IS no error and it should be. The last line you have there is the You'll see if you add in other properties that are not being deleted explicitly by the unserializer, that all the properties are being stuffed in the additional properties. |
I would also like to re-iterate this is not just a bug in this |
I just ran into this as well. It seems that the addition of a new product strings for Institutions is enough to cause the sdk to return an zero response object and no error. I ran into this when querying for Institutions by ID in the sandbox which returned a product that was not present in the local version of the sdk that I was using. I can craft a test case to show the issue if that is helpful but it took quite a while to debug why the sdk was returning a zero object and no error. |
FYI @cgfarmer4 and @aarohmankad perhaps something to look at for next month? (This one is a bit out of my depth to fix.) |
Several of the generated models have a bug in them where an empty model will be returned with no error when there is an error unmarshaling them.
A simple repro case:
Since
AccountBase
contains aType
that is anenum
there is an error unmarshaling an empty string, but that error is ignored and the additional properties are decoded, and its error is returned instead.This is a bug in the generator templates it appears to the handled correctly when
isMap
is true.The text was updated successfully, but these errors were encountered: