-
Notifications
You must be signed in to change notification settings - Fork 39
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
HUM-93 - refactor email verification pages #3009
HUM-93 - refactor email verification pages #3009
Conversation
@adrian-oleskiewicz is attempting to deploy a commit to the HUMAN Protocol Team on Vercel. A member of the Team first needs to authorize it. |
packages/apps/human-app/frontend/src/modules/worker/types/email-verification.types.ts
Outdated
Show resolved
Hide resolved
packages/apps/human-app/frontend/src/modules/worker/hooks/use-router-state.ts
Outdated
Show resolved
Hide resolved
9159142
to
424e7de
Compare
...ntend/src/modules/worker/components/email-verification/email-verification-form-container.tsx
Outdated
Show resolved
Hide resolved
@dnechay ready to review |
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 re-organize things according to their business logic purpose, not by their nature
53a03d2
to
5e639c9
Compare
@dnechay this one is ready |
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.
- We can get rid of
WorkerEmailVerificationProcessPage
component: there is no need inisLoading
state inuseEmailVerificationToken
hook, so this hook can be moved directly toEmailVerificationProcess
component and that component becomesEmailVerificationProcessPage
- No need to have
WorkerVerifyEmailPage
becauseEmailVerificationFormContainer
acts exactly like the "page"
...app/frontend/src/modules/worker/email-verification/components/email-verification-process.tsx
Outdated
Show resolved
Hide resolved
...app/frontend/src/modules/worker/email-verification/components/email-verification-process.tsx
Outdated
Show resolved
Hide resolved
...man-app/frontend/src/modules/worker/email-verification/hooks/use-email-verification-token.ts
Outdated
Show resolved
Hide resolved
...ntend/src/modules/worker/email-verification/components/email-verification-form-container.tsx
Show resolved
Hide resolved
...ntend/src/modules/worker/email-verification/pages/worker-email-verification-process.page.tsx
Outdated
Show resolved
Hide resolved
2fed918
to
9275c89
Compare
@dnechay bumping this comment as it might have been lost in the notifications 😅 |
e5677ba
to
510d22e
Compare
@dnechay resolved |
510d22e
to
3053825
Compare
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Right now when you click on "Resend verification email" it sends BE request and then nothing happens. If you try to click again - it shows An error occurred, please try again.
banner and not details, when under the hood it fails for captcha. This should be fixed (e.g. on staging we reload the page after it's successfully re-sent)
Also after sign-up it doesn't redirect to "email verification page" where it say "we've sent you email ......", it opens previous page with worker/operator sign-up (works fine on staging)
Please fix it.
In case you need different email addresses for tests purpose you can try:
- using some disposable email services
- if you have your email on Gmail - you can add
+something
to the main part, e.g.mpblocky+test-1@blockydevs.com
and it will send email to your original account
...app/frontend/src/modules/worker/email-verification/components/email-verification-process.tsx
Show resolved
Hide resolved
...ntend/src/modules/worker/email-verification/components/email-verification-form-container.tsx
Outdated
Show resolved
Hide resolved
@dnechay I fixed the email resend and redirect. I also improved notifications using the new system and fixed missing |
Issue tracking
HUM-93
Context behind the change
How has this been tested?
registered new user and checked both pages displaying correctly
Release plan
normal deploy
Potential risks; What to monitor; Rollback plan
N/A