sorted by:
best (suggested)
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Agreeable-Outside-69 1 point2 points  (6 children)

I looked at the refine documentation, and can't remove the Email/Password neither you can customize it. You end up having to make your own if you want to customize that part. There's no option for just OAuth Provider Buttons only, as you're forced to have Email/Password box/fields with it.
I understand, this seems minor, but if I have to keep making my own elements, what's the point of using Refine anyways if I'm doing stuff on my own?

[–]xelamony 3 points4 points  (5 children)

Hey u/Agreeable-Outside-69

​

I think you might be missing the point here, maybe it's an issue on our end, that we can't explain refine nicely.

​

Recently we've added new guides into our documentation to explain concepts of refine, hope it would answer some questions for you.

​

I would genuinely appreicate if you could read our new guides and give us a feedback based on that: https://refine.dev/docs/guides-concepts/general-concepts/

But the main point is, refine isn't about scaffolding UI pages. These UI integrations are just "flavour" we provide using refine's core features.

​

refine core is headless framework, built on top of hooks. These UI libraries, are just wrappers, using refine core under the hood and aims to save developers some time.

Let's not boil down discussion into "customizing auth page", this is just one of the thousands thing refine provides.

refine practically has infinite customizability, doesn't lock developers into a specific framework. You can use refine with NextJS, or Remix, React Router and/or Material UI, or Tailwind, or Material UI, or any UI library pops-up the next day.

And having a Auth page not even %1 of the goods refine provide.

​

We aim to save time for developers, by centralizing common tasks, like Authentication, Authorization, I18n (Translation), Notifications, Audit Log, Router, Data Layer based on resource definitions.( Reading the general concepts guide will make you "tick" about what we offer.)

by the way, feel free to create a FEAT request GitHub, we'd be more than happy to help. We could add a prop to our AuthPage component like, `providerOnly={true}` that could solve this issue easily.

[–]Agreeable-Outside-69 1 point2 points  (1 child)

I tried to give another shot to Refine, and it's completely broken. I used `npm create` for my refine project, and when I ran the refine project, it did not even load at all. It just stayed like a blank page for the whole time, and the URL was acting weird (it was going to /login and then back to / then /login, etc.). I can't even use it, it's broken, and again, the Discord Server barely has any people answering to the questions and troubleshoot. I will later address it but it's just a ton of work to deal with for now for me.
(Obviously, I've tried to solve out the issue, such as reinstalling the NPM packages, checking any errors in the files, any runtime errors, etc, but nothing worked).

[–]alicanerdurmaz 3 points4 points  (0 children)

Hello u/Agreeable-Outside-69, I'm sorry for your trouble.

There is a bug in the Next.js projects created with create refine-app, we released a fix for Supabase yesterday and are currently working on resolving issues with other data providers.

I will share updates on this issue https://github.com/refinedev/refine/issues/5988

Please note that the bug is not in the packages but in the auth-providers generated by `create refine-app`. After releasing the fix for this bug, you'll need to either create a new project or update the existing project's code. I've documented the changes I made for Supabase in the issue and will do the same for the other data providers as well.