supabase / auth / 10247113177

69%

push

github

fix: enforce uniqueness on verified phone numbers (#1693)

## What kind of change does this PR introduce?

With this change:
- Multiple verified phone mfa factors can exist so long as they have
distinct phone numbers (see discussion below)
- Enrolling a factor with a number that is the same as the existing
verified factor will result in a 422 status code
- Enrolling a factor with a number that is the same as another existing
unverified factor will result in the deletion of the older factor.

Also includes:
- A refactor to check for duplicate constraints at application level
then at the Postgres layer.
- A narrowing of deletion so that only unverified factors of the same
type are deleted upon first successful verification

Follow up to #1687 to support the unique constraint on phone factors.

26 of 36 new or added lines in 2 files covered. (72.22%)

9200 of 15762 relevant lines covered (58.37%)

55.23 hits per line