-
Notifications
You must be signed in to change notification settings - Fork 15
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
[Feat] #466 -회원가입 API 연동 #469
Conversation
|
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.
수고하셨습니다~~
} | ||
|
||
public var validationType: ValidationType { | ||
return .none |
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.
이 부분 없어도 validationType 기본값은 .none 아닌가용?
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.
공백 한 개만 지워주세용. . ㅎ.
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.
네네!
|
||
public enum SocialAPI { | ||
case getSocialAccount(phone: String) | ||
case changeSocialAccount(entity: ChangeSocialAccountEntity) |
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.
CoreAuthAPI에는 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.
entity 와 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.
어느 쪽이든 상관 없을 것 같아용
@@ -35,7 +37,8 @@ extension BaseAPI { | |||
public var baseURL: URL { | |||
var base = Config.Network.baseURL | |||
let operationBaseURL = Config.Network.operationBaseURL | |||
|
|||
let coreAuthBaseURL = Config.Network.coreAuthBaseURL |
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.
오옹 baseURL이 다른가요?
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.
네네 맞아용
새로운 서버를 만든거라 baseURL이 달라졌습니다
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.
good
public protocol CoreAuthService { | ||
func sendVerifyCode(_ dto: SendVerificationCodeEntity) -> AnyPublisher<Int, Error> | ||
func verifyCode(_ dto: VerifyCodeEntity) -> AnyPublisher<BaseEntity<VerifyResultEntity>, Error> | ||
func login(_ dto: LoginEntity) -> AnyPublisher<BaseEntity<CoreSignInEntity>, Error> | ||
} |
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.
AnyPublisher<Int, Error>
Error 타입을 구체화하는 것도 좋아보입니다.
발생할 수 있는 에러 모두 정의하고 그걸 기반으로 테스트 코드 짜도 좋을 것 같아요.
아니면 에러처리를 다른 곳에서 해주고 있나요?
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.
Repository에서 Domain별 Error로 변환해주도록 구현할 예정입니다.
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.
UseCase에선 해당 Error 를 catch하여 SideEffect 스트림으로 연결할 예정이구욥!
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.
Data 계층의 Error 타입 정의는 팀원들과 더 소통하고 정하면 좋을 것 같아욥
🌴 PR 요약
🌱 작업한 브랜치
🌱 PR Point
📌 참고 사항
📸 스크린샷
Data 계층 위주의 작업이라 스크린샷은 없습니다.
📮 관련 이슈