1
65%
master: 65%

Ran 05 Jul 2023 03:51AM UTC

Files 108

Run time 1s

Badge

Embed ▾

Committed 05 Jul 2023 03:44AM UTC coverage: 65.745% (+0.08%) from 65.67%

Job # 5460275786.1

Build Type

push

github

Committed by

web-flow

Commit Message

feat: allow `POST /verify` to accept a token hash (#1165)

## What kind of change does this PR introduce?
* To enable server-side redirection via an email link, we need some way
to return the session in the response body rather than in the query
fragments (`GET /verify`) because the fragments can't be parsed on the
server-side.

* By allowing `POST /verify` to accept just a token hash, a developer
would be able to set the verification URL in their email template to
point to their own endpoint
(`https://myapp.com/confirm-signup?token_hash=XXX&type=signup`) and
parse the `token_hash` param before calling `POST /verify` with the
following:

```bash
curl -X POST 'http://localhost:9999/verify' -H 'Content-Type: application/json' \ 
-d '{"token_hash": "my_token_hash", "type": "signup" }'
```

If the token hash is valid and the request is successful, this would
return the verified user's session in the response and the developer can
subsequently handle any redirection on their own.

---------

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

Run Details

7134 of 10851 relevant lines covered (65.75%)

49.13 hits per line

supabase / gotrue / 5460275786 / 1
65%
master: 65%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 5460275786.1

supabase / gotrue / 5460275786 / 1 65% master: 65%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 5460275786.1

supabase / gotrue / 5460275786 / 1
65%
master: 65%

README BADGES
x