-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
WIP Update user registration flow #168
Conversation
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Yupp. Still WIP. We're still trying to find a time to get together to finish it. |
@pdotsani @peoray Thanks for working on this this morning! Re: the bugs that you ran into...
I'm not sure that the preloaded user data generated by the script should work against that endpoint; you should be using a new user you registered.
This is because in dev, the registration email appears in the logs when you run ========= This is the process that worked for me:
(In the meantime, I'll look into figuring out how we can sidestep hardcoding this, so that it's automatically http://localhost:8000 if someone is running this locally and https://api-staging.codebuddies.org when this is deployed.)
Make sure the password is something not too common; otherwise you'll get an error. fwiw, I used After you successfully register a new user, you'll be redirected to this page: And the logs will look like this:
If you remember the logs, they pointed to a URL that said:
We can fix the hostname in the BE later (I believe there is a ticket for that on github.com/codebuddies/backend), but https://localhost:3000/api/v1/auth/registration/verify-email/?key={KEY} is the page we need to create on the FE side, and it needs to make a POST request to the http://localhost:8000/api/v1/auth/registration/verify-email/ endpoint. For example, if I paste my key into my BE app and click on the POST button: ...that's a successful response. :) Let me know if you need more screenshots/if any part of this doesn't make sense! |
cc6ded1
to
df9fa10
Compare
@pdotsani Thank you for updating the tests and the error messages! :) I think it's fine to comment out the lines in the test that aren't relevant anymore (e.g. the first and last name). Looks like this is the main TODO that remains, since logout is taken care of via
Can work on making that route if you want help! |
@lpatmo Ah ok. Didn't have enough time to get to this last week. Should be finishing up in the week or so. |
@pdotsani Thank you!! |
Thanks for the help @lpatmo. The new view and post request are working, and should be ready for review. The only additional change needed is that the url on the verification email needs to be updated to the client ( |
@pdotsani Sweet, thank you so much! I added a couple of suggestions re: things like redirecting the user to a "Verify your email" page after signing up and only showing the "Email verified" text if successful... let me know if I can clarify further or if you need any help! |
@pdotsani Thanks for pushing up your commits! Finally got around to reviewing. :) I pushed up 60f4594 which makes sure there is a dependency array in the Otherwise, looks great! I'll make a note in the backend ticket that we need to replace localhost:8000 with localhost:3000 and api-staging.codebuddies.org. |
…agination component when there is no search term, and moved it down on the page
Bumps [axios](https://github.com/axios/axios) from 0.19.0 to 0.21.1. **This update includes a security fix.** - [Release notes](https://github.com/axios/axios/releases) - [Changelog](https://github.com/axios/axios/blob/v0.21.1/CHANGELOG.md) - [Commits](axios/axios@v0.19.0...v0.21.1) Signed-off-by: dependabot-preview[bot] <[email protected]>
Co-authored-by: Linda <[email protected]>
56b2602
to
a637bbf
Compare
variant="outlined" | ||
shape="rounded" | ||
size="large" | ||
count={Math.floor(count / 10)} |
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.
small nitpick: I would move computations like these out of the rendering of components and before the return statement
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.
Good suggestion -- thanks @turretd!
API_URL: 'http://localhost:8000', | ||
}; | ||
|
||
export const config = process.env.NODE_ENV === 'development' ? dev : prod; |
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.
really love this approach 🙌
a637bbf
to
d29540f
Compare
d29540f
to
a637bbf
Compare
What type of PR is this? (check all applicable)
Context
This PR closes issue #161
Screenshots/Recordings (if there are UI changes)
Placeholder example:
![screenshot of new resource page](https://user-images.githubusercontent.com/43/23.png)
Note: you can upload a screenshot onto your PR and put it here.
Implementation Details - what was your thought process as you changed the code?
Related Tickets & Documents (Optional)
This relates to #161
Added tests?
Added to documentation (readme.md or contributing.md)?