-
Notifications
You must be signed in to change notification settings - Fork 29
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
Handle UtteranceEnd
message type
#146
Comments
We just discussed this internally. Will expose this parameter shortly. |
So this allows me to add the
|
Not the header... you want to add as a query parameter. Just this one:
|
Didn't mean to close with comment... |
Sorry typo! Meant parameter:
If I understand correctly, the router needs to handle the UtteranceEnd type: deepgram-go-sdk/pkg/api/live/v1/router.go Line 49 in 1e72d2d
|
Ahhhh that's right. There is a new message type that needs to be added. Will need to wait then until the modifications are complete. Forget about the new message type. Trying to juggle too many things right now. Will add that in a bit. |
Released for GA |
Using the
utterance_end_ms
parameter for the live api requires handling of{ type: UtteranceEnd }
. Currently here's no way to handle this in the callback interface.Perhaps an optional
UnhandledResponse
method on the callback interface could be an useful escape-hatch for new message types, rather than treating it as an error?The text was updated successfully, but these errors were encountered: