supabase / gotrue / 5353826469
65%

DEFAULT BRANCH: master
Ran
Jobs 1
Files 107
Run time 2s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 66.118% (-0.3%) from 66.448%
5353826469

push

github

web-flow 
feat: add support for Twilio Verify (#1124)

## What kind of change does this PR introduce?

Aims to add Twilio Verify Support. Twilio Verify is implemented as a
separate provider. Only one of Twilio Verify or Twilio Programmable
messaging an be selected. At this time, we only support the use of the
`whatsapp` and `sms` channels with Twilio Verify.

This will affect the:
1. Signup flow
2. Verification flow (sms and phone_change)
3. Resend

The token is still generated, but not used in the Twilio Verify flow. It
is used as a placeholder so as to try to ensure that to the OTP returned
by the Verify service can only be used with the corresponding flow it
was generated for.

## What is the current behaviour?

We support programmable messaging.

## What is the new behaviour?

Developer can toggle between using Twilio Programmable Messaging on all
flows or Twilio Verify on all flows.

## Additional context

Manual tests:

Probably need to be conducted on both Phone Change and SMS OTP
Verification:

- [x] Existing Programmable Messaging (SMS/WhatsApp)
(Signup/Verify/PhoneChange)
- [x] Twilio Verify(SMS/WhatsApp) 
- [ ] Update Frontend to include Twilio Verify

Admin methods shouldn't need to be updated to send to Twilio Verify
since admin methods don't require confirmation

---------

Co-authored-by: joel@joellee.org <joel@joellee.org>
Co-authored-by: Stojan Dimitrovski <sdimitrovski@gmail.com>

7148 of 10811 relevant lines covered (66.12%)

48.7 hits per line

Jobs
ID Job ID Ran Files Coverage
1 5353826469.1 0
66.12
 GitHub Action Run
Source Files on build 5353826469
Detailed source file information is not available for this build.