-
Notifications
You must be signed in to change notification settings - Fork 0
REAFACTOR: Domain Layer DTO 제거 #120
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
REAFACTOR: Domain Layer DTO 제거 #120
Conversation
0Hooni
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.
수고하셨습니다!
DTO랑 Entity 분리가 필요한 작업이 하나 있는것 같은데 확인 후 수정 부탁드립니다
dongglehada
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.
DTO에서 Entity로 변환할 때 통일된 형태로 변환을 진행하는 것 같지 않습니다. 프로젝트에서 일반적으로 변환하는 과정에 맞춰 통일하는 것이 좋아보이며 Entity의 네이밍 및 파일 분리가 필요할 것 같습니다.
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.
Entity가 프로젝트에서 일반적으로 사용되고 있던 네이밍이 아니라 조금 헷갈리지 않을까 하는 생각이 듭니다..!
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.
MapDomainModelConverter가 필요한 이유가 있을까요? MapPopUpStoreDTO에 메서드를 추가하는 방식 말고 왜 이방식으로 Entity로 변환하는지 궁금합니다.
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.
대부분의 DTO에서 toDoMain으로 매핑하여 처리하는것에 대한 의문에서 시작했습니다 .. 이부분만 우선적으로 진행해뒀습니다만
네트워크레이어에서 매핑까지 하는것보다 도메인 모델이 DTO에 조금의 의존성도 가지지 않으려면 분리하는게 좋지않을까 ? 란생각으로 분리하게되었습니다 DTO 마다 ToDoMain을 제각각 구현하는것보다 각기 컨버터 를 추가하는것도 나쁘지않을것 같아서요!
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.
해당 부분이 삭제되고 컨버터가 생긴것일까요? 프로젝트의 일반적인 구조와 다르게 사용한 이유가 궁금합니다
| import Foundation | ||
|
|
||
| import Alamofire | ||
| import Foundation |
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.
임포트 순서가 퍼스트 파티, 서드 파티 순서로 배치되어 있으면 좋을 것 같습니다.
…ol/iOS-renew into refactor/#117-remove-dtos-domain-layer # Conflicts: # Poppool/Poppool/PresentationLayer/Presentation/Scene/Admin/AdminReactor.swift # Poppool/Poppool/PresentationLayer/Presentation/Scene/Admin/AdminViewController.swift # Poppool/Poppool/PresentationLayer/Presentation/Scene/MyPage/Main/MyPageReactor.swift
…ub.com/PopPool/iOS-renew into refactor/#117-remove-dtos-domain-layer # Conflicts: # Poppool/Poppool/PresentationLayer/Presentation/Scene/Admin/AdminReactor.swift # Poppool/Poppool/PresentationLayer/Presentation/Scene/Admin/AdminViewController.swift # Poppool/Poppool/PresentationLayer/Presentation/Scene/MyPage/Main/MyPageReactor.swift
dongglehada
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.
DTO 사용부가 확인됩니다. 해당 부분 수정 부탁드릴게요!!
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.
Completable 사용이 좋을 것 같습니다
| )) { _, item, cell in | ||
| cell.configure(with: item) | ||
| )) { _, store, cell in | ||
| let dto = GetAdminPopUpStoreListResponseDTO.PopUpStore( |
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.
DTO 사용이 보입니다.
dongglehada
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.
LGTM!! 확인 완료하였습니다!
0Hooni
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.
LGTM!!
📌 이슈
✅ 작업 사항