Could you please add an AbortControllersignal parameter injection capability at Deepgram client initialisation time (be it through createClient() or new DeepgramClient())?
In a JS web application (with dedicated Deepgram side proxy), I want my user - through button clicks - to be able to cancel a long duration Whisper query (say the user realizes some parameters were wrong) and rerun a more relevant one (eg. with more cleverly chosen parameters).
Possible Implementation
Include the FetchParameters with the Fetch Options? Add an extra DeepgramClient and createClient parameter for Fetchparameter ?
Other information
Interesting but not so sustainable forks related to request aborting control and Deepgram:
Hello Deepgram!!
Proposed changes
Could you please add an
AbortController
signal
parameter injection capability at Deepgram client initialisation time (be it throughcreateClient()
ornew DeepgramClient()
)?For now, rather lowly exposed Restful methods allow
FetchParameters
ie.signal
passing, such as: https://github.com/deepgram/deepgram-js-sdk/blob/main/src%2Fpackages%2FAbstractRestfulClient.ts#L90Context
In a JS web application (with dedicated Deepgram side proxy), I want my user - through button clicks - to be able to cancel a long duration Whisper query (say the user realizes some parameters were wrong) and rerun a more relevant one (eg. with more cleverly chosen parameters).
Possible Implementation
Include the FetchParameters with the Fetch Options? Add an extra DeepgramClient and createClient parameter for Fetchparameter ?
Other information
Interesting but not so sustainable forks related to request aborting control and Deepgram:
https://github.com/BartoszJarocki/deepgram-js-sdk-custom-fetch/blob/main/index.ts
https://github.com/BartoszJarocki/deepgram-js-sdk (see his feat*test branch's commits).
Thanks guys!!!