-
Notifications
You must be signed in to change notification settings - Fork 1
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
Feature/issue 47 #48
Feature/issue 47 #48
Conversation
- 스케줄 엔티티 추가
- type 삭제, point 추가
- mysql 제약에 어긋나는 table/column 명 변경
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.
작업하시느라 고생하셨습니다:) 한 가지 궁금한것은
- start_time, end_time이 start_date, end_date를 포함하고 있는것으로 생각되는데, 따로 DB에 분류해서 저장하는 이유가 있으신가요?
- eg) start_date, end_date 를 프론트에 리턴해줘야하는 경우 start_time, end_time을 formatter를 사용해 YYYY-MM-DD 포맷으로 리턴해줄수 있음
@soonhankwon |
- startTime, endTime 삭제
@soonhankwon |
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.
확인했습니다. 고생하셨습니다 :)
- Tag Entity 구현 + AuthService Refactor - null 체크 메서드 안으로 이동 - 정적팩터리 메서드 사용
Quality Gate passedIssues Measures |
feat: PR을 등록한다.
작업 내용
스크린샷