fix/supabase version 1

[duncanhealy]

• fix methods used by supabase 1.0 Upgrade Supabase in auth package to supabase-js version 1.0 #1426
• update supabase package to 1.0 Upgrade Supabase in auth package to supabase-js version 1.0 #1426

[dthyresson]

@Tobbe and I realized tonight that perhaps something changed in the Supabase API that may now require a custom decoder to extract the currentUser info on the API side.

see:

redwood/packages/cli/src/commands/generate/auth/templates/auth.js.template

Line 100 in 2b18246

export const getCurrentUser = async (decoded, { _token, _type }) => {

export const getCurrentUser = async (decoded, { _token, _type }) => {
  return { ...decoded, roles: parseJWT({ decoded }).roles }
}

It is "spreading" the JWT into chars -- and not sure if it did that in the past.

This might mean that supabase should get its own decoder similar to what is done for Netlify Identity:

https://github.com/redwoodjs/redwood/blob/main/packages/api/src/auth/decoders/netlify.ts

where is

jwt.decode(token)

so that currentUser will have the decoded version of it.

Note: this does not verify the accessToken, though it probably should ... to check for expiry against the secret --- which would be then a required env.

[kiwicopple]

thanks for the tag @viperfx.

I just released the new version of gotrue-js to include @duncanhealy's commit , then bumped the version in supabase-js.

The draft supabase.ts just has a mockup of the types - not sure if it is correct

Let me know if that's all you need here, otherwise I can jump in and figure out the types. I did actually start on this but I'm swamped with our beta launch - thanks the patience 🙏

[github-actions]

📦 Packages for this PR can be downloaded from
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1474/create-redwood-app-0.21.0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1474/redwoodjs-api-0.21.0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1474/redwoodjs-api-server-0.21.0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1474/redwoodjs-auth-0.21.0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1474/redwoodjs-cli-0.21.0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1474/redwoodjs-core-0.21.0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1474/redwoodjs-dev-server-0.21.0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1474/redwoodjs-eslint-config-0.21.0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1474/redwoodjs-eslint-plugin-redwood-0.21.0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1474/redwoodjs-forms-0.21.0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1474/redwoodjs-internal-0.21.0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1474/redwoodjs-router-0.21.0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1474/redwoodjs-structure-0.21.0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1474/redwoodjs-testing-0.21.0.tgz
https://rw-pr-redwoodjs-com.s3.amazonaws.com/1474/redwoodjs-web-0.21.0.tgz

Install locally with yarn, e.g. yarn workspace web add <url>

[viperfx]

Thanks @kiwicopple

Look forward to these changes @duncanhealy

Let me know if you need help testing.

[duncanhealy]

I'm getting null back for the user object from the graphql endpoint after logging in

{"data":{"redwood":{"currentUser":{"0":"n","1":"u","2":"l","3":"l","roles":[]}}}}

looking at local dev -> might be because of this

redwood/packages/api/src/auth/decoders/index.ts

Line 17 in 1185f0f

supabase: noop,

changing typesToDecoders.supabase to netlify

with that change I get back -

{"data":{"redwood":{"currentUser":{"roles":[]}}}}

[dthyresson]

might be because of this

Hi @duncanhealy you may need to implement a decoder for supabase.

I do not think using the netlify decoder is 100% correct, because it relies on the Identity feature of Netlify to place a decoded and populated user in the context in production --- and that the token is decoded in in dev.

What is supabase setting as the token in

redwood/packages/api/src/auth/decoders/index.ts

Line 21 in 1185f0f

export const decodeToken = async (

?

Based on that will need to determine how the decode it if needed.

[Tobbe]

@duncanhealy Thanks for getting the ball rolling on this! Your work both here and over in the supabase repo(s) is much appreciated ⭐

I went ahead and upgraded to Supabase 1.0 over here #1536 and that PR has now been merged.

[Tobbe]

@kiwicopple I did the upgrade from scratch over in #1536 and so I wanted to ask if you could please take a look at the type imports. More details over in that PR.