You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I encountered the error described above while fetching data.
Those fields were missing.
I created a pull request adding those fields to the ResourceDto.
I feel like every week there is an issue or an error thrown using the sdk.
Would be great if something could be done on the API side or the sdk to try to be more stable.
Maybe a more synced deployment of changes on the API and changes on the SDK, is just a suggestion.
Thank you
The text was updated successfully, but these errors were encountered:
Thanks for this report! I believe you're talking about the issue where an old version of the SDK was using **/kwargs instead of dacite to parse JSON, which meant that it would fail if it received JSON text that included a new field not known when the API was built. That issue was fixed with #26 and should not be recurring.
Can you please confirm a few things for me?
What version of the SDK are you using?
What API call did you make?
As part of the problem reports for this issue I added tests to verify that this bug was completely fixed.
Here's a screenshot from my latest test which demonstrates that SDK version 119.0.4645 does not generate an error when fetching resources, even though those two fields are not present in that version of the SDK:
Hey,
I encountered the error described above while fetching data.
Those fields were missing.
I created a pull request adding those fields to the ResourceDto.
I feel like every week there is an issue or an error thrown using the sdk.
Would be great if something could be done on the API side or the sdk to try to be more stable.
Maybe a more synced deployment of changes on the API and changes on the SDK, is just a suggestion.
Thank you
The text was updated successfully, but these errors were encountered: