Bug report

At the moment the peerDependency is at version "@supabase/supabase-js": "^1.11.6"

The latest supabase version is "@supabase/supabase-js": "^1.24.0"

To keep react-supabase up to date we better update the to the latest.

Observed Behavior

Missing optional data field when using auth.signUp()

https://supabase.io/docs/reference/javascript/auth-signup

Expected Behavior

react-supabase to provide the same interface as supabase-js

Bug report

Description / Observed Behavior

Recursive execution of real-time hook when filter option is passed.

Expected Behavior

Open a websocket connection and subscribe to changes

Repro Steps / Code Example

const Chats: React.FC<ITabsProps<'Chats'>> = ({}) => {
  const [{ data }] = useRealtime<DB.Member>(
    'members',
    {
      select: {
        columns: 'id',
        filter: (query) => query.eq('userId', '94a9aa95-c794-404a-9a37-7f424b215ebb'), // Works when this line is removed
      },
    }
  )

  useEffect(() => console.log(data), [data])

  return (...)
}

Additional Context

{
    "@supabase/supabase-js": "^1.24.0",
    "expo": "~42.0.1",
    "react": "16.13.1",
    "react-dom": "16.13.1",
    "react-native": "https://github.com/expo/react-native/archive/sdk-42.0.0.tar.gz",
    "react-supabase": "^0.2.0"
  }

This might be a fault of mine. I can't read the HTTP request or console logs as Firefox just breaks when I execute this.

Bug report

Description / Observed Behavior

Use something like useInsert and force an error (insert null value in required column). Either wrap the call in a try/catch block, or utilize the .catch syntax for callbacks. The catch block never hits. The exception is swallowed, and returned in the errors property instead. This is not the behavior I would expect, because any libraries that can be used with promises (react-toastify in my case) cannot be directly used with this library.

Expected Behavior

I would expect exceptions to propagate up as they traditionally do, or provide some means to opt-out of this behavior.

Repro Steps / Code Example

const [_, insertEvent] = useInsert<CalendarEvent>('calendar_event');

try {
  const insertFunc = await insertEvent({
    // insert nothing to force a validation error
  })
  } catch (err) {
    console.log(err) //<-- this will never be hit
  }

  const insertFunc = await insertEvent({
    // insert nothing to force a validation error
  }).catch(error => {
    console.log(error); // <-- this will never be hit
  });

Additional Context

The issue can be worked around by wrapping the call

  const insertFunc = async () => {
    const { data, count, error } = await insertEvent({
      // force error
    })
    if (error) throw error;
    return { data, count };
  }

This could be made suitably generic to wrap any call, but feels like this shouldn't be necessary.

Error message:

Code used:

Bug report

Whenever I include the provider in my Expo app I get:

 ERROR  Unhandled promise rejection [RangeError: Maximum call stack size exceeded (native stack depth)]

Description / Observed Behavior

 ERROR  Unhandled promise rejection [RangeError: Maximum call stack size exceeded (native stack depth)]

Expected Behavior

No errors

Repro Steps / Code Example

Additional Context

latest supabase js and react-supabase

Bug report

useAuthStateChange fails in @supabase/supabase-js v2+

Description / Observed Behavior

The useAuthStateChange hook throws a n.unsubscribe is not a function error on v2 versions of supabase/supabase-js.

Expected Behavior

Hook does not throw page breaking error and returns documented values.

Repro Steps / Code Example

https://codesandbox.io/s/sharp-snow-vdzivd?file=/src/App.tsx:311-312

Additional Context

react-supabase version - 0.2.0
@supabase/supabase-js - 2.2.3

The authStateChanged listener has since been updated to return a subscription object with the unsubscribe function.

I guess this is a question of compatibility since this library is only rated for v1 but are there plans for v2 support and or are PRs updating the existing hooks welcome?

Title says it all

Bug report

Description / Observed Behavior

I am using the useRealtime functionality like this:

const [{ data: payments, error, fetching }] = useRealtime(
         "payments",
        {
            select: {
                columns: 'id, created_at, amountToPay, user (userId, displayName, email)',
                filter: (query) => query.eq("state", OPEN)
            }
        },
        (data, payload) => data.id === payload.id);

The problem I am facing is, that after an update occurs with the given query and filters, I can not get the user.

Expected Behavior

Just like fetching, when the data is updated, I recieve the complete row with foreign relations updated.
I would expect, that when in the code above the amountToPay changes, that I recieve the whole updated row with the foreign relationship of user with it.

useSubscription and useRealtime are completely broken right now because the signature for subscription has changed in v2. See https://supabase.com/docs/reference/javascript/subscribe

Bug report

The useSignIn() hook does not work correctly.

Description / Observed Behavior

Try to use the sign-in hook, and successfully log in (the user is created in the Supabase console), but when I'm redirected, the new session is not loaded by the hook, despite that being the core functionality:

const [{ error, fetching, session, user }, signIn] = useSignIn();
console.log({ user, session });
// { user: undefined, session: undefined }

Expected Behavior

After signing in, the hook should return the user and session data.

const [{ error, fetching, session, user }, signIn] = useSignIn();
console.log({ user, session });
// something other than all undefined

Repro Steps / Code Example

Included.

Additional Context

Latest version. Basic sign-in. No idea why this would not work out of the box.