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
SDK - support of API versions #2
Comments
@christinelu , @JiamingFB - you might see this as an enhancement - I see this as a blocker. |
Hi |
Hi Nirfeldman, In the version just released, you can specify API version when calling constructor of APIContext. The limitation is that the SDK code reflects only the fields/params/enums in current version. If you want to set a param/field which only exists in older version, you can refer to the README.md “Customisation and debugging” section for missing params/fields. |
Got you: |
It seems like this issue has been open for more than a few months now. We have made many changes in the SDK since then, including releasing a new version. If you can repro your specific issue with the latest version of the SDK, please create a new issue or comment here with further details. |
Although it seems like it is designed for supporting multiple versions of the API I see few issues:
This way a client of the library is really able to choose which versions to use, you can maintain one master branch supporting few versions in parallel and once a version is deprecated, you delete the package.
Hope this makes sense
@christinelu FYI
The text was updated successfully, but these errors were encountered: