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

Alternatives missing in result type #16

Closed
wodka opened this issue Dec 7, 2021 · 2 comments
Closed

Alternatives missing in result type #16

wodka opened this issue Dec 7, 2021 · 2 comments

Comments

@wodka
Copy link

wodka commented Dec 7, 2021

What is the current behavior?

there should be alternatives in the result type

Steps to reproduce

enable alternatives and try to consume them.

Expected behavior

The result should have typed alternatives

Please tell us about your environment

  • Operating System/Version: *
  • Language: TypeScript
  • Browser: *

Other information

Alternatives are referenced in the API https://developers.deepgram.com/api-reference/ but not in the more detailed documentation

@wodka wodka changed the title Alternatives missing Alternatives missing in result type Dec 7, 2021
@michaeljolley
Copy link
Contributor

Hi @wodka, alternatives should exist currently on the individual channel returned in the transcript. Their location on a result would look like:

const response = await deepgram.transcription.preRecorded(fileSource, {
  punctuate: true,
});
const channel0Alternatives= response.results.channels[0].alternatives

Am I misunderstanding?

@wodka
Copy link
Author

wodka commented Dec 7, 2021

no you are completely right - I missed this. Thank you!

@wodka wodka closed this as completed Dec 7, 2021
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