feat: expose role and transcriptType on Transcript event#13
Open
gitaumoses4 wants to merge 1 commit into
Open
Conversation
The Vapi WebSocket sends `role` ("user" or "assistant") and
`transcriptType` ("partial" or "final") on transcript messages,
but the SDK was discarding them. This makes it impossible to
distinguish user speech from assistant speech in real-time.
This change adds both fields to `Event.Transcript` so consumers
can identify the speaker and finality without relying on the
delayed `ConversationUpdate` event.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Vapi WebSocket sends
role("user" or "assistant") andtranscriptType("partial" or "final") on transcript messages, but the SDK was discarding them. This makes it impossible to distinguish user speech from assistant speech in real-time.This change adds both fields to
Event.Transcriptso consumers can identify the speaker and finality without relying on the delayedConversationUpdateevent.