Philipp Steinrötter

Thanks for reporting! What supabase-js / postgrest-js version are you using?

this is fixed with the latest release. before, we weren't compatible with the latest `supabase-js`. :)

That's very weird. Do you see any difference in what you are doing vs what we are doing in tests [here](https://github.com/psteinroe/supabase-cache-helpers/blob/main/packages/postgrest-server/tests/query-cache.test.ts)?

ahh sorry, I misunderstood the issue earlier! So you are using postgrest-server alongside the react-query adapter? And passing the result of this function to react-query throws. ```ts function getChallenges(client: TypedSupabaseClient,...

hey @colespencer1453, thanks for your interest in contributing to this library. Highly appreciated! we are using pnpm v8 still, although despite the updated lockfile I dont think there will be...

it is, public and storage are always exposed. What errors do you get?

that is indeed weird! Are you using the supabase cli version declared in the repo?

I think this is related to how react query works. In SWR, we set `revalidateIfStale` to `false` ([docs](https://supabase-cache-helpers.vercel.app/configuration)) and explicit set `revalidate` to `false` when doing the mutation https://github.com/psteinroe/supabase-cache-helpers/blob/3a1f88d91d2c7483428ac9985ec01a4062bd4f8b/packages/postgrest-swr/src/cache/use-upsert-item.ts#L40 I...

Hey @rgathman, thanks for opening the issue. Unfortunately, we cannot use rpcs in the useMutation hooks. But you can still do this: first, setup the mutation using a plain useSWrMutation...

Thanks for the quick response! Our use case is that the api schema will serve as our public api, and changing all queries in our app that target the public...