[FIX] 닉네임 유효성 검사 API 응답 변경 #148
Merged
Conversation
This file contains 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
from 409 Conflict to 200 OK
타인 nickname이어서 중복일 때 던지던 409 Conflict 로직 삭제
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.
Related Issue
Key Changes
nickname validation에서 타인 nickname과 중복일 경우 response 변경
To Reviewers
닉네임 유효성 검사 API에서
였는데
2.는 유효성을 검사하는 것일 뿐이지 해당 리소스로 put patch post하는 것이 아니기 때문에 409보다는 200이 좋을 것 같다는 클라의 제안에 수정할 예정입니닷