-
Notifications
You must be signed in to change notification settings - Fork 1
[fix] 하나의 웨이블존에 여러개의 저장한 리스트를 추가할 수 있도록 로직 변경 #173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
f725de5
[refactor] 웨이블존 저장 및 조회 관련 swagger 이름 변경
seung-in-Yoo b1df4ea
[fix] 하나의 웨이블존에 여러개의 리스트를 저장하도록 로직 변경
seung-in-Yoo 76198c7
[refactor] 핸들러 메서드명 의미에 맞게 변경
seung-in-Yoo 89b5995
[refactor] 코드리뷰 반영
seung-in-Yoo fa9f0f8
[fix] 페이지 관련 0 -> 1 로 변경
seung-in-Yoo File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
9 changes: 0 additions & 9 deletions
9
src/main/java/com/wayble/server/user/dto/UserPlaceRequestDto.java
This file was deleted.
Oops, something went wrong.
4 changes: 0 additions & 4 deletions
4
src/main/java/com/wayble/server/user/dto/UserResponseDto.java
This file was deleted.
Oops, something went wrong.
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
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
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
API 문서 방향이 실제 동작과 반대입니다: ‘웨이블존에 리스트 추가’ → ‘리스트에 웨이블존 추가’로 수정 필요
서비스 호출은 웨이블존을 여러 리스트에 추가하는 동작(
addZoneToPlaces)인데, 현재 문구는 “웨이블존에 리스트를 추가”로 반대로 서술되어 있어 오해의 소지가 큽니다. Swagger 문구를 아래처럼 교정해 주세요.📝 Committable suggestion
🤖 Prompt for AI Agents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@coderabbitai 웨이블존에 리스트를 추가든 리스트에 웨이블존을 추가든 결국 디비에 placeId, waybleZoneId 매핑 레코드가 생겨서 결론은 둘이 동일한거 아니야? 서비스 로직에서 잘못된 부분 없는거같은데
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@seung-in-Yoo 맞습니다! 데이터베이스 관점에서는 결국 동일한
placeId,waybleZoneId매핑 레코드가 생성되므로 기능적으로는 완전히 동일하네요.제가 API 문서의 표현에 너무 세세하게 집착했던 것 같습니다. 현재 구현이 요구사항을 올바르게 충족하고 있고, 사용자 입장에서 혼란이 없다면 현재 상태로도 충분히 좋습니다.
서비스 로직도 정상적으로 구현되어 있어서 문제없어 보입니다! 🙂