Go SDK should accept a context for all remote calls

[romanlevin]

Currently the Go SDK uses an internal context object for all remote calls. Among other things, this means users of the SDK can't specify a timeout or cancel a call to Trinsic.
trinsic-id/sdk#155

[fundthmcalculus]

@romanlevin for my understanding, what you want is to be able to provide, or alter, the context object used?

[romanlevin]

@fundthmcalculus in general yes, but specifically it's common (universal?) practice in Go API design to accept a context object as the first argument for every blocking function.

[fundthmcalculus]

Right on. I didn't for the initial prototype, will add that as part of the async support that's coming soon.

…

On Thu, Oct 21, 2021, 12:43 Roman Levin ***@***.***> wrote: @fundthmcalculus <https://github.com/fundthmcalculus> in general yes, but specifically it's common (universal?) practice in Go API design to accept a context object as the first argument for every blocking function. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <trinsic-id/sdk#147 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD7QPF5ABQCXZYQBNDIEW6DUIA7J3ANCNFSM5GOARHAQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[fundthmcalculus]

@romanlevin just added context support to main. Please test again.
trinsic-id/sdk#155