-
Notifications
You must be signed in to change notification settings - Fork 35
Add Sign Up and Login Pages (#66) #84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Validation? |
AbhinavReddy-Dev
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also the validations are not completely working including empty fields and formats.
PantryNodeReact/src/pages/login.tsx
Outdated
| function Copyright(props: any) { | ||
| return ( | ||
| <div> | ||
| login | ||
| <Button onClick={() => navigate("/")}> Submit</Button> | ||
| </div> | ||
| <Typography variant="body2" color="text.secondary" align="center" {...props}> | ||
| {'Copyright © '} | ||
|
|
||
| Pantry Node | ||
| {' '} | ||
| {new Date().getFullYear()} | ||
| {'.'} | ||
| </Typography> | ||
| ); | ||
| }; | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we have this component in a separate file under Components folder since we are using it twice again in signup page?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure that is something can be done later I wanted to get this merged today so we could talk to the backend team about having them then provide the endpoints for authentication.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did this one
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did all of these approve this
| ); | ||
| } | ||
|
|
||
| const theme = createTheme(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please check the src/index.tsx file, we already have a theme provider wrapped around the whole app.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
okay I can reference the theme. The home page isn't following correct color codes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did all of these approve this
| </Link> */} | ||
| </Grid> | ||
| <Grid item> | ||
| <Link href="/signup" variant="body2"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible to have another link for 'forgot password?'?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
its there it is just commented out because I don't want the people to focus on how to have session with Token I want the focus being on getting the Login Workflow Correct and Talking to the backend team.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did all of these approve this
|
|
||
| const theme = createTheme(); | ||
|
|
||
| export default function SignUp() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have you given a thought about switching between the components of 'Login', 'Signup', and 'ForgotPassowrd'? under a single page based on the user selection?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did all of these approve this
Also, according to latest model I checked, we would required separate fields for |
|
@prestonmasseyblake Everything else looks good to me! Just some minor updates before we can merge it tonight. |
Validations still ain't working on my codespace :/ @AbhinavReddy-Dev |
|
I do see that the email format is not working as expected, after review by @DevangRaval1 . |
Oh I see yeah, thanks. Validations works now! |
|
As per schema is in main docs/[Foodbank ER Diagram.png]
As per docs/Foodbank ER Diagram.png schema, @prestonmasseyblake change the placeholder name to as |
|
Can we place try and avoid doing work in personal forks. This should be done in a feature branch so users don't need to clone a new repo to review, it messing with issues tracking, referencing changes, etc. |
|
Why don't we get this merged and open up a new issue for the email, phone and password, validation. |
|
I can do that but I would like this to be merged so the other teams can see what the login, signup look like and start working on the authentication part in terms of the backend and thinking about how they are going to implement forgot password. I can write the validation functions later today or tomorrow. Pull requests should not be dozens of commits. |
We tend to develop on the personal_branch then squash and merge into frontend branch and in the end create a pull request once confirmed by the peers. |
That sounds great. This PR doesn't seem to be following those practices though. |
so for the feature branches, should we checkout from |
Where ever you checkout from, merge it into 'frontend' initially by creating a pull request to check for any changes necessary and then finally create a pull request to main. We would like to keep the main branch clean from all trivial commits. |
so basically following steps involved, correct if I miss anything @AbhinavReddy-Dev
|
You got it 60-70% correct.
If anyone has a better approach please let us know here. |
gotcha! So, what should we do with this PR? I suppose, for now we can make exceptional for this pr, merging with |
@AbhinavReddy-Dev or we can actually change the |
That looks great to me, people just need to remember that if you are using a fork there would be an additional step of pushing local for changes to
I think all PR's to main need to come from repo feature branches not forks, so this PR should be canceled and recreated from a feature branch in our shared repo. We should avoid doing work in forks if at all possible and keep everything as a feature branches so anyone can see what commits are going on without needing to find a different repo. |
ok makes sense |
And we had discussed this one
Yeah and we did discuss this in #38 that not to use forks. |
Yeah, we can then merge it into main with a pull request, that should solve the issue of forks. @prestonmasseyblake What do you say? We can then merge it with a proper pull request following the practice for this repo. |
parthpandey1
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM

This pull request adds the sign up and login pages to the project, addressing issue #66. Users can now create new accounts and log in to access the features of the application functionality needs to be implemented by backend team now it just pushes you to homepage. This will enhance the user experience and increase the functionality of the project. The new pages are designed to be user-friendly and intuitive, with clear instructions and error messages to guide users through the process. By adding these essential features, we can improve the overall usability and accessibility of the application.
See FIGMA for what the designs look like