supabase / auth / 9596939146

push

github

fix: update MaxFrequency error message to reflect number of seconds (#1540)

## What kind of change does this PR introduce?

Currently we use a constant value on number of seconds left before a
developer can send a follow up email confirmation. This can prove
confusing if developer has a custom setting for `MaxFrequency` on `Sms`
or `SMTP`

We change some core email related routes to show the exact number of
seconds. This includes `signup`, `magic_link` and `email_change`

The rest will follow should this change roll out smoothly. Tested the
three flows locally by triggering the max frequency limit and checking
that the number of seconds show up as expected.

0 of 8 new or added lines in 4 files covered. (0.0%)

8699 of 15083 relevant lines covered (57.67%)

54.45 hits per line