Skip to content
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

refactor: 수동 매칭, 자동 매칭 요청 형식, 타입 통일 #109

Merged

Conversation

soyesenna
Copy link
Collaborator

@soyesenna soyesenna commented Feb 5, 2025

수동 매칭에는 description, departureTime이 더 있음

📌 관련 이슈

관련 이슈 번호 #108
Close #108

🚀 작업 내용

PR에서 작업한 내용을 설명

📸 스크린샷

image

📢 리뷰 요구사항

리뷰어가 특별히 봐주었으면 하는 부분이 있다면 작성

수동 매칭에는 description, departureTime이 더 있음
@soyesenna soyesenna self-assigned this Feb 5, 2025
List<Integer> members,
Integer expectedTotalCharge
List<Long> members,
int expectedTotalCharge
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

프론트 측에서 값을 필수로 넣어주나요??
아니면 0이 저장돼서 의도치 않은 흐름이 될 수도 있을 것 같아서

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

유효성 검증 추가하겠습니다!!

Copy link
Member

@huncozyboy huncozyboy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

고생하셨습니다 !

로직상 문제는 없어보여용
저희가 친구초대할때 닉네임으로 검색을 하는 로직(검색 리스트 반환)이 추가가 된다면,
필드의 재변경이 필요할거같다는 생각입니다

@soyesenna soyesenna merged commit 18679c3 into dev Feb 5, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Feat]: #[Issue number] [자동매칭,수동매칭 요청형식통일]
3 participants