-
Notifications
You must be signed in to change notification settings - Fork 0
[Feat] #208 - 애플 로그인 구현 및 소셜로그인 타입별 예상되는 사이드 이펙트 대응 #209
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
Conversation
sangyup12
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.
리브랜딩 이미지까지 ㄷㄷ. 진짜 얼마 안 남았다!! 저도 빠르게 마무리 해보겠습니다!
|
|
||
| import KakaoSDKUser | ||
| import KakaoSDKAuth | ||
| import AuthenticationServices |
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.
와! 애플로그인 등장
| var temporarySignUpData: LoginResponseEntity? | ||
| var nickname: String = "" | ||
| var name: String = "" | ||
| var socialType: String = "" |
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.
userId 추가해서 사용하도록 하겠습니다. 감사합니다
| @@ -151,7 +159,7 @@ extension OnboardingViewModel { | |||
| jobs: selectedJobCategory | |||
| ) | |||
|
|
|||
| let result = await signupUseCase.execute(request: requestData, preSignUpToken: authManger.preSignupToken) | |||
| let result = await signupUseCase.execute(request: requestData, preSignUpToken: authManger.preSignupToken!) | |||
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.
p2
엔티티와 토큰 강제 언래핑하는 거 크래쉬 위험 괜찮을까여?
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에 nullable한 필드가 많이 생겼고, 이 dto를 사용하던 엔티티를 최대한 기존 코드 수정없이 바꾸려다가 그냥 강제 언래핑했어요...
좀 더 신경쓰면 엔티티를 나눈다던지.. 방법이 있긴 한데 최대한 기존 코드들 안 건드리려고 요렇게 함..
Yeonnies
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.
애플로그인까지.. 최고!!
| // | ||
|
|
||
| import SwiftUI | ||
| import Combine |
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.
p3
오.. 컴바인
|
|
||
| actor TokenRefresher { | ||
| static let shared = TokenRefresher() | ||
| nonisolated let tokenExpiredSubject = PassthroughSubject<Void, Never>() |
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.
p3
nonisolated 신기하네여
🌴 작업한 브랜치
feat/#208✅ 작업한 내용
📟 관련 이슈