Handle network requests in Airrecord::Client #54
Closed
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.
Fixes #44.
While I was at it, I thought it would be helpful to draw firmer boundaries between
Table
andClient
. Specifically,Table
no longer manipulates network requests directly — it just asksClient
to make requests, and letsClient
handle escaping, parsing, errors, etc.I think this will make it easier to add features to
Table
, like finder methods (#19), validations, etc. But I may have gotten a bit carried away.