-
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
Reimplement how we return responses #7
Comments
SDK Return Types
This is similar to some of our SDK functions that do not wrap the return values in a class.
Creating resources from resource models using the
This kind of structure may not be the best for our SDK because we do not have a lot of Model types to benefit from this kind of abstraction. Having Models to abstract away JSON types are good enough for our use case and would allow for easier developing. |
Currently we return responses from the various functions as ad-hoc custom classes which are dynamically created based on what we get from the API.
I think this needs to be improved. Look at other SDKs and see what they do and see if we can adopt it.
TBD
The text was updated successfully, but these errors were encountered: