[Proposal] Unified Client interface #56
Draft
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.
Adds build targets support to Client class and drafts a proposal for unified endpoint/resource handling.
Notes about some decisions:
undefined
values but still be documentedbuild_target
endpoint is an interesting example because it groups targets by version name but we want to access each build target separately (which would be possible in endpoint V2). So we're normalizing the data and providing the interface which will remain constant even after switching the backing endpointError
building/handling pattern that combines our three implementations mentioned in the ClubHouse story