-
Notifications
You must be signed in to change notification settings - Fork 5
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] - 여행기 Service 코드 리팩터링 #504
Merged
Merged
Changes from all commits
Commits
Show all changes
44 commits
Select commit
Hold shift + click to select a range
f73fe03
style: 메서드 순서 수정
Libienz 459b5e7
feat: TravelogueDay의 주인 되는 여행기 속성 세터 오픈
Libienz 9e18de6
feat: Travelogue 양방향 연관관계 편의메서드 작성
Libienz 2e0bd21
feat: TravelogueDay의 TraveloguePlace 추가 양방향 연관관계 편의메서드 작성
Libienz f2afac0
feat: TraveloguePlace의 TraveloguePhoto 추가 양방향 연관관계 편의메서드 작성
Libienz e6358d6
refactor: 양방향 연관관계를 통해 Dto 매핑 과정에서 엔티티 연관관계를 맺도록 수정
Libienz 4692659
refactor: 양방향 연관관계를 통해 Dto 응답 Dto 매핑 과정 단순화
Libienz 9bb8111
refactor: 사용하지 않는 메서드 제거 개선
Libienz f9c116d
refactor: 반정규화된 엔티티로부터 likeCount를 조회하도록 DTO 매핑 로직 개선
Libienz fdaefcd
feat: 여행기에 대한 특정 멤버의 좋아요가 존재하는지 확인하는 기능 구현
Libienz 93b5cbe
refactor: TravelogueFacadeService 양방향 연관관계를 이용한 매핑 과정 추상화 적용
Libienz aaebaec
refactor: TravelogueLikeService 사용하지 않는 메서드 제거 개선
Libienz 873294b
refactor: 불필요한 서비스 호출 제거 개선
Libienz 89efae0
refactor: 필터 여부에 따른 분기를 facade가 아닌 하위 서비스로 이동 개선
Libienz 08b5dbf
refactor: TravelogueLikeService 사용하지 않는 메서드 제거 개선
Libienz 8f42809
refactor: TravelogueLikeService 파사드 하위 서비스는 뷰를 다루지 않도록 개선
Libienz c7d8eb2
fix: 여행기 콘텐츠가 수정되지 않는 문제점 해결
Libienz 6c30061
refactor: 파사드 하위의 TravelogueTagService가 도메인을 다루도록 계층 분리 개선
Libienz 8752c64
refactor: 사용하지 않는 서비스 클래스 제거 개선
Libienz 1ebae52
refactor: 과한 메서드 분리 제거 개선
Libienz 4119f50
feat: 여행기 속 사진 컨텐츠를 영구 저장소로 옮기는 서비스 구현
Libienz 1b3a1c1
refactor: 사용하지 않는 메서드 제거 개선
Libienz 5f9dbb8
refactor: S3 컴포넌트를 Facade가 아닌 하위 서비스가 사용하도록 추상화
Libienz 09c510c
test: 이미지 복사 로직 테스트 모킹 단순화 개선
Libienz 6dc2714
chore: develop branch merge
Libienz ad3191d
test: 특정 여행기에 특정 멤버가 좋아요했는지 확인할 수 있는 기능 테스트 작성
Libienz cce9109
test: 여행기 저장 서비스 메서드 테스트 작성
Libienz 70cb200
refactor: 사용하지 않는 메서드 제거 개선
Libienz 3286ac9
refactor: 메서드 배치 호출 순서에 맞게 수정
Libienz 0093013
refactor: 사용하지 않는 메서드 제거 개선
Libienz b9dde68
refactor: Guest용 뷰 로직 DTO 내부로 응집 개선
Libienz b0c2dcc
refactor: TravelogueFacadeService의 여행기 업데이트 메서드가 변경 내용을 반환하도록 개선
Libienz a7e5510
test: 여행기 수정 테스트 doesNotThrow -> 변경 내용 확인 테스트로 개선
Libienz 72d9e83
refactor: ImagePermanentSaver -> PerputationService로 이름 변경 및 서비스 컴포넌트화
Libienz c37d8f1
refactor: memberService 메서드 이름 수정 (다른 서비스 메서드의 이름과 컨벤션 통일)
Libienz daa2246
test: 여행기 양방향 연관관계 편의 메서드 테스트 작성
Libienz 842c40b
test: TravelogueDay 양방향 연관관계 편의 메서드 테스트 작성
Libienz a57579b
test: TraveloguePlace 양방향 연관관계 편의 메서드 테스트 작성
Libienz d079652
refactor: Setter update로 이름 변경 (사용처 제한 명세 역할)
Libienz 99f67be
refactor: 오버로딩 제거 -> 메서드 시그니처에 명세 상세화
Libienz 6fc7d99
refactor: 이미지 S3 영구 저장소 이동 로직을 Facade로 이동 (서비스 계층 분리 의미 명확하게)
Libienz 720c5cf
Merge branch 'develop/be' into feature/be/#496
Libienz c27e99a
Merge branch 'develop/be' into feature/be/#496
Libienz 8b77665
refactor: 메서드 명 변경 작업 미반영 -> 반영 조치
Libienz 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 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 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 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 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 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 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 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 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 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 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 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 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 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 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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
이번 pr에서 할 일은 아닌 것 같긴 한데 양방향 연관관계를 활용해서 clear 없이 update를 수행하도록 바꾸면 더 좋겠네요.
update 로직 개선으로 추후 진행해봐도 좋을 것 같습니다!
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.
이슈 파놓았습니다~ #514
변경 감지로 진행되면 깔끔할 것 같아요 다만 프론트랑 명세는 맞추어 봐야겠네요!