supabase-community / auth-ui

Pre-built Auth UI for React
https://supabase.com/docs/guides/auth/auth-helpers/auth-ui
MIT License
487 stars 121 forks source link

Clicking on magicLink -> Client side warning #49

Closed jeremyisatrecharm closed 1 year ago

jeremyisatrecharm commented 1 year ago

Bug report

I think it still works but gives the following warning:

next-dev.js?3515:20 Warning: Received `false` for a non-boolean attribute `loading`.

If you want to write it to the DOM, pass a string instead: loading="false" or loading={value.toString()}.

If you used to conditionally omit it with loading={condition && value}, pass loading={condition ? value : undefined} instead.
    at button
    at Button (webpack-internal:///./node_modules/@supabase/auth-ui-react/dist/esm/src/components/UI/Button.js:57:5)
    at div
    at Container (webpack-internal:///./node_modules/@supabase/auth-ui-react/dist/esm/src/components/UI/Container.js:47:5)
    at div
    at Container (webpack-internal:///./node_modules/@supabase/auth-ui-react/dist/esm/src/components/UI/Container.js:47:5)
    at form
    at MagicLink (webpack-internal:///./node_modules/@supabase/auth-ui-react/dist/esm/src/components/Auth/interfaces/MagicLink.js:31:5)

Describe the bug

A clear and concise description of what the bug is.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

Code:

    <Auth supabaseClient={supabaseClient} appearance={{ theme: ThemeSupa }} magicLink={true} />

Just click on "send a magic link email" with chrome dev tools open and you should see this error.

I am using the latest version of Next.js and React.

  1. Go to '…'
  2. Click on '…'
  3. Scroll down to '…'
  4. See error

Expected behavior

A clear and concise description of what you expected to happen.

Screenshots

If applicable, add screenshots to help explain your problem.

System information

Additional context

Add any other context about the problem here.

silentworks commented 1 year ago

This is a warning, not a bug. Please upgrade to the latest version of the library 0.2.3 which should fix this warning.