search

savannah-Silica / e-commerce-api

E-commerce platform API: Customers can browse products, add items to their cart, checkout, and make payments.
MIT License
2 stars 8 forks source link

User Authentication #7

Open zablon-oigo opened 10 months ago

zablon-oigo commented 10 months ago

Authenticate users who want to purchase products based on their email or username

Collins-Omariba commented 10 months ago

Assigned. I think you should create a users app and put all functionality there. But I am open to suggestions on how you want to do it . After settling on a way, confirm first here then proceed with the development.

zablon-oigo commented 10 months ago

I will create a separate app for users, including a custom profile model and login, signup, and logout functionality. Before I proceed, Please let me know if you have any specific fields in mind that you want to include in the user profile.

mpiers110 commented 10 months ago

@zablon-oigo https://drawsql.app/teams/oma-collins/diagrams/e-commerce-api

Maishmike commented 10 months ago

@zablon-oigo in the sign out what's your view on having the sign out redirect to home rather than login

zablon-oigo commented 10 months ago

@zablon-oigo in the sign out what's your view on having the sign-out redirect to home rather than login

It can be updated, but my view was that if someone logs out they can still be able to view the product list, but if they add any product to the cart or want to view product details they be required to sign in

mpiers110 commented 10 months ago

@zablon-oigo I'm working on the cart, I have already created the logic and the models. I'll add the condition of requiring signing in to add products to the cart

zablon-oigo commented 10 months ago

@zablon-oigo I'm working on the cart, I have already created the logic and the models. I'll add the condition of requiring signing in to add products to the cart

great

DDLoga commented 10 months ago

someone working on login pages? path('login/', sign_in, name='login'), path('logout/', sign_out, name='logout'), path('signup/', sign_up, name='signup'),

Maishmike commented 10 months ago

@zablon-oigo ooh yes that makes sense.

zablon-oigo commented 10 months ago

someone working on login pages? path('login/', sign_in, name='login'), path('logout/', sign_out, name='logout'), path('signup/', sign_up, name='signup'),

Please expound kindly. do you mean the templates or the logic views?

DDLoga commented 9 months ago

more about the templates. @Collins-Omariba Not sure what's the deliverable of this API (I.E. what API Payload, format etc....) can you please share your vision and expectations..... would be glad to serve;)

Collins-Omariba commented 9 months ago

more about the templates. @Collins-Omariba Not sure what's the deliverable of this API (I.E. what API Payload, format etc....) can you please share your vision and expectations..... would be glad to serve;)

The project isn't restrictive, the final thing should be a working e-commerce API ( I have seen guys creating templates which is still ok) and there is an emphasis on maximum learning since that is the aim of the community . The only thing to be careful about is any change should be documented or properly done for it to be easy for other devs to contribute too.

mpiers110 commented 9 months ago

@DDLoga @mpiers110 @Collins-Omariba @zablon-oigo @Maishmike How about we work on the backend fully and we create basic templates for rendering the views, and then we'll create an app for the api side of it?

Collins-Omariba commented 9 months ago

I am ok with this. But first open an issue to update the main readme and properly explain how the project is to go , for new contributors to be able to know .

@DDLoga @mpiers110 @Collins-Omariba @zablon-oigo @Maishmike How about we work on the backend fully and we create basic templates for rendering the views, and then we'll create an app for the api side of it?

zablon-oigo commented 9 months ago

@DDLoga @mpiers110 @Collins-Omariba @zablon-oigo @Maishmike How about we work on the backend fully and we create basic templates for rendering the views, and then we'll create an app for the api side of it?

@mpiers110 I'm okay with it, but first @Collins-Omariba what is the state of the project?

Collins-Omariba commented 9 months ago

@DDLoga @mpiers110 @Collins-Omariba @zablon-oigo @Maishmike How about we work on the backend fully and we create basic templates for rendering the views, and then we'll create an app for the api side of it?

@mpiers110 I'm okay with it, but first @Collins-Omariba what is the state of the project?

Can you elaborate more on what you mean by state ?

zablon-oigo commented 9 months ago

@DDLoga @mpiers110 @Collins-Omariba @zablon-oigo @Maishmike How about we work on the backend fully and we create basic templates for rendering the views, and then we'll create an app for the api side of it?

@mpiers110 I'm okay with it, but first @Collins-Omariba what is the state of the project?

Can you elaborate more on what you mean by state?

Sorry, I meant progress cause, for the past week, all of you have been silent

Collins-Omariba commented 9 months ago

@DDLoga @mpiers110 @Collins-Omariba @zablon-oigo @Maishmike How about we work on the backend fully and we create basic templates for rendering the views, and then we'll create an app for the api side of it?

@mpiers110 I'm okay with it, but first @Collins-Omariba what is the state of the project?

Can you elaborate more on what you mean by state?

Sorry, I meant progress cause, for the past week, all of you have been silent

sorry for the late reply, I am a little busy. There aren't any deadlines , the main focus is to collaborate . You can contribute at any time and the same applies to everyone else

mpiers110 commented 9 months ago

@zablon-oigo I'm done with the products app. I'm awaiting your part on authentication so that I can add '@login_required'😄to the views and integrate the shopping cart