anubhav06 / eatit Goto Github PK

The backend needs to be restructured into a more easy to understand structure.
Currently it has a separate folder for API which should be removed and needs to be merged with the parent directory.

When a user completes a payment, they are redirected to either a success_url page (UserProfile.js) in case the payment is successful or a cancel_url page (CheckoutCancelPage.js) in case the payment is cancelled.

In both these cases pressing the back button will take the user back to the payment's page. Here, the back button needs to be disabled, preventing the user from going back.

Going back to the payment's URL again is not a security issue, but to improve the user's experience, the back button needs to be disabled

Improving the way frontend is designed. This includes either of the following conditions:

1. Modifying the existing CSS
2. Improving the way React code is coded.
   Maybe splitting into more components for a better understanding (open to suggestions )

Add unit testing and GitHub Actions

The CSS is not completely responsive and breaks in certain views

When a new user/restaurant registers, they have to go to the login page to fill the credentials again to login.

When they register, they should be automatically be logged in rather than having to manually do so.

Is your feature request related to a problem? Please describe.
Right now, the restaurants it shows, are only in Delhi, India. I think there's a location api out there, which if there is would be great if you check it out and see if you can use it for the project.

Describe the solution you'd like
Use the location api, to get the location of the user on the site (call a popup asking for permission for the site to access location)(the location shouldn't go back to you, maximum the country, eg: India or state can go back to you but preferably nothing goes back to you), with the state and area found, search for restaurants, via Google Maps, Google Business, etc.

Little confusing, I don't think I explained it well, but hope you understood :D

Backend needs more unit testing specifically checking Twilio's API and Stripe's API

While a form is being submitted, till it gets back a response from backend, a loading visual should appear something (not exactly) like the below one:

So far this needs to be done in the following forms:

1. Login Form
2. Registration Form

Does the cart page use something close to the Swiggy Template?

Currently the required fields for Registration are:
Username, Password, Confirmation Password, Email, Mobile Number and the user is logged in based on their username and password.

The username fields needs to be removed as it's kind of redundant keeping in mind what this project is i.e. a food ordering web application (with no use of a username).

User authentication should be done based on the email and password rather than username and password.

This will be similar to restaurant's authentication, where restaurant owner's are authenticated based on their email and password and no username is asked during login/registration

PROBLEM

The current authentication method i.e. JWT, generates a new Access Token and Refresh Token on each load of webpage.
These new tokens are then stored in the backend database ( as the djangorestframework-jwt) works this way. This is a bad design as this would just increase the db size whenever a client loads the page.

EXPECTED BEHAVIOUR
The new Access Token and Refresh Token should just be generated when the old token has expired. (and not on each load of the page)

Add a footer with the following text. The footer should be visible on every page

Incase of any bugs / feature request, please report here

When a user adds/removes an item from a cart, the API makes a call to the backend.
Here, the buttons needs to be disabled once they are pressed, and then re-enabled once the API gets back a response from the frontend.
You can add any visual representation to do this. Maybe some loading visual ?

Working on this issue will be similar to how login/registration page submit button works. It is disabled till the API gets back a response from the backend.