This came out of an internal need for a project I was working on incorporating the SDK, and represents about the extent of time I have to contribute to Features API support at this time. If someone else can pick up from where this started, that would be great.
I have programmatically and manually tested all of the the FeaturesClient methods in the context of the project described above, and everything seems to be working. In particular, the API has different pagination scheme, currently handled by overriding Paged.__next_link, that could perhaps be incorporated directly into Paged, since the as-of-yet-unimplemented Analytics API uses the same pagination scheme.
Related Issue(s):
Oddly enough, we do not seem to have an issue for Features API support yet.
Proposed Changes:
For inclusion in changelog (if applicable):
Add FeaturesClient to support the Features API
PR Checklist:
[ ] This PR is as small and focused as possible
[ ] If this PR includes proposed changes for inclusion in the changelog, the title of this PR summarizes those changes and is ready for inclusion in the Changelog.
[ ] I have updated docstrings for function changes and docs in the 'docs' folder for user interface / behavior changes
[ ] This PR does not break any examples or I have updated them
Includes: list_collections, create_collection, list_features, create_features
This came out of an internal need for a project I was working on incorporating the SDK, and represents about the extent of time I have to contribute to Features API support at this time. If someone else can pick up from where this started, that would be great.
I have programmatically and manually tested all of the the FeaturesClient methods in the context of the project described above, and everything seems to be working. In particular, the API has different pagination scheme, currently handled by overriding Paged.__next_link, that could perhaps be incorporated directly into Paged, since the as-of-yet-unimplemented Analytics API uses the same pagination scheme.
Related Issue(s):
Oddly enough, we do not seem to have an issue for Features API support yet.
Proposed Changes:
For inclusion in changelog (if applicable):
PR Checklist: