Feature/forgot password #39
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nsw/trainee-fool-24t3 into feature/forgot-password
|
to clarify, 'attendee' was made redundant so that a 'user' can be both be an attendee of an event and involved in a society, without needing multiple different accounts. i think we might've discussed this as an option during early planning but decided against it because it would take a bit more effort but.. she'll be right |
…ests to verify otp expiration from 70 seconds to 1 second
Deploying foolish-pyramids with
|
| Latest commit: |
b09acf1
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://b3a0bbb7.foolish-pyramids.pages.dev |
| Branch Preview URL: | https://feature-forgot-password.foolish-pyramids.pages.dev |
lachlanshoesmith
approved these changes
Dec 12, 2024
|
thanks isaac!! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
not too sure what is going on with the attendee changes but it appeared when i merged with main somehow - may be related to backend changes being made related to deprecation of Attendee table in the database