Added support for tier to ensure backward compatibility

akshaylb commented 3 months ago

Proposed changes

Types of changes

What types of changes does your code introduce to the community Go SDK? Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update or tests (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] I have lint'ed all of my code using repo standards
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments

dvonthenen commented 3 months ago

Hi @akshaylb

Yea, not sure why that is missing. They are in the other SDKs. But thanks for catching this.

dvonthenen commented 3 months ago

Hi @akshaylb

I'm waiting for feedback on reconnect bug which I should hear back by end of day. If this is super urgent, this is the first commit after the last release (which occurred yesterday). So it's safe to just pin to this commit ID a48acc88c2aaa5c29b2727cfff966d0ae1300237.

akshaylb commented 3 months ago

Thanks @dvonthenen , this isn't super urgent! I can wait for your scheduled next release.

deepgram / deepgram-go-sdk