-
Notifications
You must be signed in to change notification settings - Fork 302
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
[FeatureRequest] Add CancellationToken pass-through to async request methods #514
Comments
This issue has been added to our internal backlog to be prioritized. Pull requests and +1s on the issue summary will help it move up the backlog. |
Interested and willing to work on this |
Any updates on this? |
Any news ? |
I'm trying to pass a cancellation token to Twilio.Rest.Verify.V2.Service.VerificationCheckResource.CreateAsync(... params) but, of course, I thought of making a pull request, however here's a snippet from the Issues and Bugs in the Contributing to twilio-csharp guidlines.
Methods that could accept a cancellation token are in such files, and therefore, contributers cannot help in this particular issue. |
Issue Summary
I am currently building UiPath activities to wrap this SDK. UiPath is built on Windows Workflow Foundation. Workflow activities provide a cancellation token so that activities can be interrupted/ continued at a later time/ provide general async support. It would be nice if the async twilio activities exposed this parameter and passed it through to HttpClient so that requests can be cancelled. Is this something that is in the backlog or is being planned in the future?
Generally, .net libraries with async methods support this parameter with a default of CancellationToken.None as to not cause breaking changes in existing code. The .NET HttpClient supports this parameter, but the Twilio SDK does not provide it.
Code Snippet
In TwilioRestClient.cs
In SystemNetHttpClient.cs
Each async version of the request functions would have this optional parameter added (Excluded here due to the fact there are a large number of them).
The text was updated successfully, but these errors were encountered: