Update Email Verification methods #251
Merged
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
jonatascastro12
changed the title
|
Current dependencies on/for this PR:
This comment was auto-generated by Graphite. |
This was referenced Sep 6, 2023
AshGodfrey
approved these changes
Sep 6, 2023
pkg/users/client.go
Outdated
| type CompleteEmailVerificationOpts struct { | ||
| type VerifyEmailCodeOpts struct { | ||
| // The unique ID of the User whose code will be verified. | ||
| User string | ||
| // The verification token emailed to the user. |
There was a problem hiding this comment.
small nit but probably should change comments to reflect this too
jonatascastro12
deleted the
feature/usrld-1047-update-verifiyemailcode-endpoint-to-handle-nested-user
branch
Merged
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.
Description
CreateEmailVerificationChallenge->SendVerificationEmailCompleteEmailVerificationChallenge->VerifyEmailCodeResponse of both methods is changed to
UserResponsewhich contains a nestedUserDocumentation
Does this require changes to the WorkOS Docs? E.g. the API Reference or code snippets need updates.
If yes, link a related docs PR and add a docs maintainer as a reviewer. Their approval is required.