fix: specific error messages for user registration#90
Open
Luna161 wants to merge 1 commit into
Open
Conversation
RegisterUser now returns (user, error_message) tuple instead of just None on failure. Error messages cover: missing fields, password requirements, duplicate email, database errors, and creation failures. The register view now returns descriptive JSON error messages instead of empty responses. Also handles JSON decode errors and mail sending failures gracefully. Closes Jespermagician#34
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #34
Problem
Users.RegisterUser()only returnedNoneon failure with no indication of what went wrong. The register endpoint returned an empty{}response.Fix
RegisterUsernow returns(user, error_message)tuple —(user, None)on success,(None, "description")on failureprint()statements from RegisterUser