-
Notifications
You must be signed in to change notification settings - Fork 0
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
[TNT-142] 트레이니 연결 화면 작성 완료 #41
Conversation
e1d1d5f
to
552bc1b
Compare
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.
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.
네 좋아요! 반영해놓겠습니다 :)
func verifyTrainerInvitationCode(_ code: String) async throws -> Bool | ||
/// API Call - 트레이니 - 트레이너 연결 API 호출 | ||
func connectTrainer(_ info: TraineeConnectInfo) async throws -> ConnectionInfo |
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.
이 부분 저희 상의한대로 Repo로 빼면 될것같습니다! 이외의 모든 DefaultUseCase도 반영 부탁드려요!
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 작성해서 올리겠습니다!
📌 What is the PR?
🪄 Changes
🌐 Common Changes
🔥 PR Point
전에 작성했던대로, DIContainer를 활용한 UseCase 사용방식 그대로 Trainee Repository, Usecase를 작성했습니다.
추후 추가 작성 필요시 그대로 작업해주시면 될 것 같습니다.
작성 화면 중 겹치는 화면들은 UserType을 넣으면 해당 타입 기능이 수행될 수 있게 작성했습니다.
반영하시면 좋을 것 같아요.
💭 Related Issues