Skip to content

[Bug] Model Listen topic segments with the Listen response shape #102

Description

@GregHolmes

Summary

The generated Listen V1 response models results.topics as the Read API SharedTopics shape (results.topics.results.topics). Listen responses instead provide results.topics.segments, so typed access to topic segments is unavailable.

Affected version

0.10.0

Evidence

src/main/java/com/deepgram/types/ListenV1ResponseResults.java declares Optional<SharedTopics> topics. SharedTopics only models a results property, not segments; the payload is retained only through additionalProperties.

Expected behavior

Listen topic detection responses should expose results.topics.segments through dedicated generated Java types.

Acceptance criteria

  • Correct the API definition so Listen and Read use distinct topic response schemas.
  • Regenerate the Java SDK rather than directly patching generated model files.
  • Add a deserialization regression test for a Listen topic-segments response.
  • Confirm the generated response reaches segments through a typed getter.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions