It's a good point to see you are applying the Hilt for DI pattern on projects to manage dependencies. Besides that, I am wondering why do you need the TokenAuthenticatorEntryPoint inside the CustomAccessTokenInterceptor 🤔 It looks like a workaround solution to provide the preferenceManager and tokenRepo. Can we get rid of this and perform the injection when the class's instance is initialized instead?
It's a good point to see you are applying the Hilt for DI pattern on projects to manage dependencies. Besides that, I am wondering why do you need the
TokenAuthenticatorEntryPoint
inside theCustomAccessTokenInterceptor
🤔 It looks like a workaround solution to provide thepreferenceManager
andtokenRepo
. Can we get rid of this and perform the injection when the class's instance is initialized instead?https://github.com/kaungkhantsoe/NimbleTest/blob/dc472deabbd5c405e37def6289ef9822ed17cb5a/app/src/main/java/com/kks/nimbletest/util/interceptors/CustomAccessTokenInterceptor.kt#L33-L38