-
Notifications
You must be signed in to change notification settings - Fork 0
1차 MVP 기능 개선 #30
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
1차 MVP 기능 개선 #30
Conversation
닉네임 최대 글자 제한
This reverts commit ba523ea.
Jeongminyooa
left a comment
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.
코드 확인했으!!! 코멘트 한번만 확인해줘~ 넘 고생많았다....
| @Getter | ||
| @Setter | ||
| public class HttpStatusDTO<T> { | ||
| private int statusCode; |
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.
추후에 http status에 쓰이는 변수들 enum으로 관리 가능하게 재정의하면 좋을 듯!
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.
2.0 배포하면서 추가로 작업할게!
| package donmani.donmani_server.appversion.entity; | ||
|
|
||
| public enum PlatformType { | ||
| Android, |
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.
대문자로 통일하는게 낫지 않을까? e.g. AOS, IOS 등
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.
|
|
||
| @GetMapping("/calendar/{userKey}") | ||
| public ResponseEntity<ExpenseResponseDTO> getExpensesCalendar( | ||
| @GetMapping("api/v1/expenses/calendar/{userKey}") |
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.
서버 사이드는 버전 정책 어떻게 가져갈지 한번 얘기해봐야겠다
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 살리느라 클래스(DTO), 메소드, URL에 V1, V2 막 섞여있는데, 클라쪽 API 붙이는 작업 마치면 이것도 다시 손볼게
| userRepository.save(newUser); | ||
|
|
||
| UserRegisterResponseDTO response = new UserRegisterResponseDTO(user.getUserKey(), user.getName()); | ||
| response = new UserRegisterResponseDTO(true, newUser.getUserKey(), newUser.getName()); |
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.
여기서는 왜 builder를 안 쓴건쥐 궁금해!
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.
직관성...?
#️⃣ 연관된 이슈
[feature-29] 1차 MVP 기능 개선 #29
📝 작업 내용