verify email before invoking store API #139
Draft
Conversation
This file contains hidden or 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
tobihagemann
requested changes
Jan 19, 2026
| this._feedbackData.errorMessage = ''; | ||
| $.ajax({ | ||
| url: REQUEST_HUB_MANAGED_URL, | ||
| url: VERIFY_EMAIL_URL, // REQUEST_HUB_MANAGED_URL, |
Member
There was a problem hiding this comment.
Can we delete REQUEST_HUB_MANAGED_URL?
Member
Author
There was a problem hiding this comment.
Sure, as soon as we have a plan for how email verification shall be implemented on the frontend. As noted above, this is currently just a PoC
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.
Warning
DO NOT MERGE
This is just a tech demo atm
This change sends the data to the "verify email" endpoint, which (if configured correctly) will forward it to the final store endpoint on completion of the verification process.
Run
npm run serveto use the staging endpoints