-
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
Feat/#13 카카오 로그인 기능 설정 #28
The head ref may contain hidden characters: "feat/#13-\uCE74\uCE74\uC624-\uB85C\uADF8\uC778-\uAE30\uB2A5-\uC124\uC815"
Conversation
import dagger.hilt.android.HiltAndroidApp | ||
|
||
@HiltAndroidApp | ||
class OworiApplication: Application() { | ||
override fun onCreate() { | ||
super.onCreate() | ||
KakaoSdk.init(this, "6c28960f69d4c7f00043b02d890dd6e0") |
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.
서버키 같은 상수들은 따로 strings.xml 이나 별도의 configuration.xml 로 관리하는게 좋을거 같습니다.
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.
별도의 configuration.xml에서 관리할 수 있도록 하겠습니다!
import javax.inject.Inject | ||
|
||
@HiltViewModel | ||
class LoginViewModel @Inject constructor() : BaseViewModel() { | ||
class LoginViewModel @Inject constructor(@ApplicationContext private val context: Context) : BaseViewModel() { |
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.
context를 주입받지 않고 그냥 AndroidViewModel을 사용해도 될 거 같습니다.
혹은 해당 context가 필요한 로직들은 activity에서 관장하고, 그 이후의 비즈니스 로직만 viewmodel에서 관리해도 될것으로 보입니다.
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.
넵 context 필요한 로직은 viewmodel에서 분리하겠습니다!
@bamin0422 conflit 해결해서 머지~! |
오케오케!! |
🧨이슈
🔍 상세 내용 (해결 내용)
💡 참고자료 및 공유할만한 자료 (선택)
❕후속 진행 이슈