dima/supabase
1
0 Fork 0
mirror of https://github.com/supabase/supabase.git synced 2026-10-05 09:25:06 +03:00
Code Issues Packages Projects Releases Wiki Activity

fix: small errors 😅

Browse Source 
* fix: small error

* fix: small error
This commit is contained in:
0xflotus authored and GitHub committed 2021-05-05 23:50:50 +02:00
1 parent eceb748251
commit 6fb9c407ac
2 files changed
+4 -4
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

web/docs/learn/auth-deep-dive/gotrue.md
+2 -2
View File
@@ -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({
@@ -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)
web/docs/learn/auth-deep-dive/jwts.md
+2 -2
View File
@@ -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
{
@@ -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)