Skip to content
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

Typing in _type.py is out of date with what is actually returned from API #157

Closed
will-btrt opened this issue Oct 24, 2023 · 2 comments
Closed

Comments

@will-btrt
Copy link

What is the current behavior?

the types in _types.py don't actually represent what is returned from the API. Specifically I am using the Paragraphs feature, and the API returns paragraphs.paragraphs.speaker which I would like to access, but the typing does not list the speaker as a field (which is optionally there if you specify diarization).

Steps to reproduce

  • Use the Python SDK
  • Specify Smart formatting and Diarization
  • Transcribe something
  • Use typing
  • Try access the the speaker field from within the paragraphs and your typing will complain because the SDK doesn't actually contain the possible fields returned from the API.

Expected behavior

I would expect to see speaker: Optional[int] here

Please tell us about your environment

We want to make sure the problem isn't specific to your operating system or programming language.

  • Operating System/Version: macOS 12.5.1
  • Language: Python
  • Browser: Chrome

Other information

deepgram-sdk==2.11.0

@davidvonthenen
Copy link
Contributor

This should be fixed in this PR
#177

@davidvonthenen
Copy link
Contributor

This should be addressed in the latest PR. You can either check using main branch or wait for the next published release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants