-
Notifications
You must be signed in to change notification settings - Fork 144
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
fix: check if 'lineTypeIntelligence' property exists #3758
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -16,6 +16,7 @@ import { | |
InvalidOrApprovedVerificationError, | ||
InvalidPhoneNumberPhoneProviderError, | ||
InvalidTypePhoneProviderError, | ||
MissingTypePhoneProviderError, | ||
PhoneCodeInvalidError, | ||
PhoneProviderConnectionError, | ||
PhoneProviderRateLimitExceededError, | ||
|
@@ -57,6 +58,9 @@ export const TwilioClient = (): IPhoneProviderService => { | |
fields: "line_type_intelligence", | ||
}) | ||
// https://www.twilio.com/docs/lookup/v2-api/line-type-intelligence#type-property-values | ||
if (!lookup.lineTypeIntelligence) { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. do we really want to stop sending the code if There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
return new MissingTypePhoneProviderError() | ||
} | ||
if (lookup.lineTypeIntelligence.type === "nonFixedVoip") { | ||
return new InvalidTypePhoneProviderError("nonFixedVoip") | ||
} | ||
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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'm not sure we should have Critical for this error? not sure in what scenario we would not have this, but this seems to be expected from twilio at times and not much we could do when that scenario arises?
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.
this should not be critical, we cant control external service response
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.
My thinking was to just flag this as critical for now but to identify what's happening more clearly so that we can look into if we should downgrade it to not alert us, or if it can serve as a proxy that something is wrong with the general service.
In the last month or so it's only comes up 4 time out of thousands of calls (traces)
If we think it's better to swallow the error alert now though I can make that change