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

[ADD] 루틴 추가 중 예전 루틴 체크 로직 추가 #75

Merged
merged 4 commits into from
Jan 12, 2024

Conversation

thguss
Copy link
Member

@thguss thguss commented Jan 11, 2024

✨ Related Issue

📝 기능 구현 명세

image image

🐥 추가적인 언급 사항

리팩토링.. 머리 감싸면서 쥐어짜냈는데 더 좋은 코드가 떠오르지 않네용.. 🥺
좀 더 좋은 리팩토링 방식이 있다면.. 훈수 제안 언제나 환영입니다 ㅎㅁㅎ

@thguss thguss added add 작업 추가 sohyeon 소현 작업 labels Jan 11, 2024
@thguss thguss self-assigned this Jan 11, 2024
Copy link
Contributor

@Chan531 Chan531 left a comment

Choose a reason for hiding this comment

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

수고하셨습니다~! 반영이 몹시 빠르군요 ㄷㄷㄷ 고수고수

return memberDailyRoutineRepository.save(new MemberDailyRoutine(member, routine));
}

private MemberDailyRoutine createOldRoutines(
Copy link
Contributor

Choose a reason for hiding this comment

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

이전 루틴을 가져온다는 부분에서 create보단 get같은 단어가 더 어울릴 거 같은데 혹시 어떻게 생각하시나요?

Copy link
Contributor

Choose a reason for hiding this comment

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

저는 뭔가 create는 그대로 하는데 New를 사용하셨으니까 Old -> Prior은 어떠신지? 근데 Prior은 흐음.. 한 번 고민만 해주세요

Copy link
Member Author

@thguss thguss Jan 12, 2024

Choose a reason for hiding this comment

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

흐음 의논이 좀 필요하겠네요 🧐
@Chan531 이전 루틴을 가져오긴 하지만 결국은 MemberRoutine으로 한 번 만들기 때문에 create를 사용했고,
@csb9427 New-Old 워딩이 대비되는 데 직관적이라고 생각해서 사용하긴 했거든요!

지피티한테도 한 번 물어보고 결정해보겠습니다-! 리뷰 감사해요 :)

Copy link
Member Author

Choose a reason for hiding this comment

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

@csb9427 old로 사용하도록 하겠습니다! 좀 더 직관적이라는 것에 공감이 되었어요-!
image

Copy link
Member Author

Choose a reason for hiding this comment

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

@Chan531 찾아보니 복구의 개념에 가까워서 create와 get보다는 re-가 더 직관적인 것 같아요! 가장 직관적으로 생각되는 recreate로 반영하도록 할게요!
image

Copy link
Contributor

@csb9427 csb9427 left a comment

Choose a reason for hiding this comment

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

역시 천재 개발자 소현 오늘부터 제 목표로 삼겠습니다.

return memberDailyRoutineRepository.save(new MemberDailyRoutine(member, routine));
}

private MemberDailyRoutine createOldRoutines(
Copy link
Contributor

Choose a reason for hiding this comment

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

저는 뭔가 create는 그대로 하는데 New를 사용하셨으니까 Old -> Prior은 어떠신지? 근데 Prior은 흐음.. 한 번 고민만 해주세요

@thguss thguss merged commit 5aa6b22 into develop Jan 12, 2024
1 check passed
@thguss thguss deleted the fix/#74-routine-fix-api branch January 12, 2024 03:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
add 작업 추가 sohyeon 소현 작업
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[ADD] 루틴 추가할 경우 이전에 삭제한 루틴에 있으면 그대로 가져오는 로직 추가
3 participants