Katerina Skroumpelou

Also, I'm talking with the docs team, so that we can improve our docs around this. Thank you all.

I have created this project here as a playground: https://github.com/mandarini/test-edge I can invoke all CRUD functions without an issue. - Here is my `cors.ts` file: https://github.com/mandarini/test-edge/blob/main/supabase/functions/_shared/cors.ts As @GAURAV-DEEP01 very correctly...

Check out the docs here: * https://supabase.com/docs/guides/auth/auth-hooks/custom-access-token-hook * https://supabase.com/docs/guides/auth/jwts?queryGroups=language&language=ts Specifically this: https://supabase.com/docs/guides/auth/jwts?queryGroups=language&language=ts#using-custom-or-third-party-jwts

I think [this PR](https://github.com/supabase/supabase-js/pull/1817) should have fixed this issue. It's available on the latest version of `supabase-js`. Can you please try it out? In the same time, we are working...

@fadymak i think this should be good to go now, right?

I will be parking this PR for now, since it will be a breaking change. We will consider this change for our v3 release. Thank you @SumitKumar-17

Do you find that this issue needs to reopen?

Reopened. Thanks for the detailed explanation @uncvrd and the input @j4w8n. To fix this properly, we need a server-side change in GoTrue to include a Supabase-specific identifier in the implicit...

Thanks for the PR @Athaxv! This is a great feature request and the client-side implementation looks good. However, the storage server's REST API (`/object/*` routes) doesn't currently handle the Content-Encoding...

Thank you for raising this issue @IdellHeaney and thanks @7ttp for the proposed solution! After internal discussion, we believe that adding an explicit `dispose()` method to clean up the `BroadcastChannel`...