fix: Add speaker_name field to SimpleTranscriptSegment response model #3991
+1
−0
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.
Summary
speaker_namefield in developer API responses_add_speaker_names_to_segments()but stripped by Pydantic because it wasn't in the modelProblem
PR #3962 added
speaker_nameto transcript segments, but the field only appeared in webhooks, not in the developer API (/v1/dev/user/conversations). This was becauseSimpleTranscriptSegmentPydantic model didn't include the field.Fix
Added
speaker_name: Optional[str] = NonetoSimpleTranscriptSegmentmodel.