-
Notifications
You must be signed in to change notification settings - Fork 54
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
feat(client): Export DoSync
/DoAsync
and RequestInfo
.
#289
Conversation
This PR is required to truly make the Client API changes in #285 usable from a client extension implementation. This is currently in draft form, mainly to capture some proposals on how to best do this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Naming suggestions
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved, but some minor comments.
@hpidcock That's fair. I'd be fine with |
Closing this because it's basically exposing an implementation detail from the Pebble client that might not be suitable for other clients. Will iterate on a new proposal soon. |
This patch exports
client.Do{Sync,Async}
methods and moves the arguments to aRequestInfo
struct. The idea is that applications extending Pebble can call these helper methods in order to perform HTTP requests to the daemon through an extended client (see #285).