Skip to content

Commit

Permalink
fix: small errors 😅
Browse files Browse the repository at this point in the history
* fix: small error

* fix: small error
  • Loading branch information
0xflotus authored May 5, 2021
1 parent eceb748 commit 6fb9c40
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
4 changes: 2 additions & 2 deletions web/docs/learn/auth-deep-dive/gotrue.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ You'll have to make sure your google app is verified of course in order to reque

[Gotrue-js](https://github.com/supabase/gotrue-js) (and also [gotrue-csharp](https://github.com/supabase/gotrue-csharp), [gotrue-py](https://github.com/j0/gotrue-py), [gotrue-kt](https://github.com/supabase/gotrue-kt), and [gotrue-dart](https://github.com/supabase/gotrue-dart)) are all wrappers around the gotrue API endpoints, and make for easier session management inside your client.

But all the functionality of gotrue-js is also available in supabase-js, which uses gotrue-js internall when you do things like:
But all the functionality of gotrue-js is also available in supabase-js, which uses gotrue-js internally when you do things like:

```jsx
const { user, session, error } = await supabase.auth.signIn({
Expand All @@ -69,4 +69,4 @@ In the next guide we'll be looking at how to setup external OAuth providers: Wat
- Watch [Part Three: Policies](/docs/learn/auth-deep-dive/auth-policies)
<!-- - Watch [Part Four: GoTrue](/docs/learn/auth-deep-dive/auth-gotrue) -->
- Watch [Part Five: Google Oauth](/docs/learn/auth-deep-dive/auth-google-oauth)
- Sign up for Supabase: [app.supabase.io](https://app.supabase.io)
- Sign up for Supabase: [app.supabase.io](https://app.supabase.io)
4 changes: 2 additions & 2 deletions web/docs/learn/auth-deep-dive/jwts.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ Well, the JSON object starts out looking something like this:
}
```

`sub` is the "subject", which is usually the uuid of the user. `name` is self explanitory, and `iat` is the unix timestamp at which the token was created. Many JWTs will also have an `exp` which is the data at which the token is set to expire, and can no longer be used. These are some of the standard fields you may find in a JWT, but you can pretty much store whatever you want in there, for example:
`sub` is the "subject", which is usually the uuid of the user. `name` is self explanatory, and `iat` is the unix timestamp at which the token was created. Many JWTs will also have an `exp` which is the data at which the token is set to expire, and can no longer be used. These are some of the standard fields you may find in a JWT, but you can pretty much store whatever you want in there, for example:

```js
{
Expand Down Expand Up @@ -176,4 +176,4 @@ Now that you understand what JWTs are and where they're used in Supabase, you ca
- [Part Three: Policies](/docs/learn/auth-deep-dive/auth-policies)
- [Part Four: GoTrue](/docs/learn/auth-deep-dive/auth-gotrue)
- [Part Five: Google Oauth](/docs/learn/auth-deep-dive/auth-google-oauth)
- Sign up for Supabase: [app.supabase.io](https://app.supabase.io)
- Sign up for Supabase: [app.supabase.io](https://app.supabase.io)

0 comments on commit 6fb9c40

Please sign in to comment.