fix(#173): throw 409 on user already exists #185
Merged
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 #173
PR-Codex overview
This PR focuses on modifying the
register_user
function to return a tuple containing aStatusCode
and an error message when a user registration fails, specifically returning aStatusCode::CONFLICT
for existing users. Additionally, it introduces a new test case for this behavior.Detailed summary
register_user
fromResult<StatusCode, String>
toResult<StatusCode, (StatusCode, String)>
.StatusCode::CONFLICT
when user registration fails due to an existing user.returns_409_when_user_exists
to verify that a conflict status is returned when trying to register an existing user.