-
Notifications
You must be signed in to change notification settings - Fork 2
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
[Voice] - support for the whole API #27
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job on PR!
We have here a discrepancy of types accepted by api function and a models, I think it would be nice to unify them to reduce confusion.
Also, the test just checking the instance, it would be nice to have check response field values as well for a more robustness.
@@ -32,6 +32,9 @@ def __init__( | |||
self.auth_origin = "auth.sinch.com" | |||
self.numbers_origin = "numbers.api.sinch.com" | |||
self.verification_origin = "verification.api.sinch.com" | |||
self.voice_applications_origin = "callingapi.sinch.com" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's not used, and overrieded below, but it would be a dot after calling
self.voice_applications_origin = "callingapi.sinch.com" | |
self.voice_applications_origin = "calling.api.sinch.com" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://developers.sinch.com/docs/voice/api-reference/voice/tag/Applications/
I think there is a separate endpoint for Applications
:
url = "https://callingapi.sinch.com/v1/configuration/numbers"
Thanks! When it comes to the |
For the loose enum handling (aligned with our ADR) I have an investigation ticket prepared: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving!
Besides that we decided to investigate a new approach for enums in the future
DEVEXP-306
DEVEXP-299