Would you create a "Create new user" component with an API, or just keep the API on the page?

Lars Hæhre · 2024-07-05T19:41:48.242+00:00

I'm new to Component thinking so I have a question on what makes most sense: I want a new user to be able to signup (using Supabase). Would you create a component for example named "SignupUser" and then put the API to signup in Supabse inside that component? Or would you just create the API on the Signup page (and don't put this in a component)?As for now I don't see using that component on any other pages, so it will be the only place on the entire website/app that I signup a user. (Meaning: It won't be reused anywhere else).

Lars Hæhre
1 year ago
I'm new to Component thinking so I have a question on what makes most sense: I want a new user to be able to signup (using Supabase). Would you create a component for example named "SignupUser" and then put the API to signup in Supabse inside that component? Or would you just create the API on the Signup page (and don't put this in a component)?

As for now I don't see using that component on any other pages, so it will be the only place on the entire website/app that I signup a user. (Meaning: It won't be reused anywhere else).
@Lars Hæhre
I'm new to Component thinking so I have a question on what makes most sense: I want a new user to be able to signup (using Supabase). Would you create a component for example named "SignupUser" and then put the API to signup in Supabse inside that component? Or would you just create the API on the Signup page (and don't put this in a component)?

As for now I don't see using that component on any other pages, so it will be the only place on the entire website/app that I signup a user. (Meaning: It won't be reused anywhere else).
Lucas G
1 year ago
There was an API discussion earlier that might help
https://discord.com/channels/972416966683926538/972416966683926541/1258820628279197831
In this case, it doesn't make much difference either way
Only if the signup form could/will be used in multiple places
Lars Hæhre
1 year ago
Yeah I actually read it. And that was very useful 😄
Thanks for responding this fast btw @Lucas G !
Lars Hæhre
1 year ago
Another question, maybe it should be in a separate thread but I'll try first here:
When making a component (named Button) to be used for all Buttons in the app.

Would the logical thing be to create a custom Event, for example called ButtonClicked - that is triggered whenever the button is clicked. Meaning that event is triggered in the Page (that contains the Button component). And then do whatever I want that button to do? (In this case, send an API)
It feels quite cumbersome, but it might be the correct way? 😄
Lucas G
1 year ago
Yeah that's fine. Easiest way to pass the click event
Lars Hæhre
1 year ago
Okay. Thanks again!
👍1

Would you create a "Create new user" component with an API, or just keep the API on the page?

Lars Hæhre

Lucas G

Lars Hæhre

Lars Hæhre

Lucas G

Lars Hæhre