Introduce a hybrid client that can multiplex across the GraphQL & REST APIs #257
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
19 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This hybrid client will prefer the GraphQL API in most circumstances, but will fall back to the REST API if it thinks its querying too much data. It also understands how to back off from the REST API and will instead return cached data to prevent server throttling.
The interface should be the same as the GraphQL client, meaning it's largely a drop-in replacement (except for needing a different
Authobject that contains anapi_keyfor communicating with the REST API.This PR also includes cleanups to the REST client to differentiate it from the hydrawiser-compatible client.
There are also a number of other cosmetic and test fixes included.