如何在 Hilt dagger 中重新初始化单例组件？

Nitish 发表于 Dev

尼蒂什

我的项目中有一个改造模块，登录前我想使用没有标题的改造，但登录后我想使用带头的改造使用 Hilt Dagger。我怎样才能做到这一点？

@Module
@InstallIn(SingletonComponent::class)
object RetrofitDi {


@Provides
fun getBasePath(): String {
    return "http://abcd.com/"
}

@Provides
fun providesLoggingInterceptor(): HttpLoggingInterceptor {

    return HttpLoggingInterceptor().setLevel(HttpLoggingInterceptor.Level.BODY)
}

@Provides
fun providesOkHttpClients(@ApplicationContext context: Context, sharedPreference: SharedPreference, httpLoggingInterceptor: HttpLoggingInterceptor): OkHttpClient {
    val okhttpClient = OkHttpClient.Builder()
    okhttpClient.addInterceptor(httpLoggingInterceptor)
    okhttpClient.callTimeout(60, TimeUnit.SECONDS)
    okhttpClient.connectTimeout(60, TimeUnit.SECONDS)
    okhttpClient.writeTimeout(60, TimeUnit.SECONDS)
    okhttpClient.readTimeout(60, TimeUnit.SECONDS)
    val token = sharedPreference.getStringData(SharedPreference.AUTH_KEY)
    val user_id = sharedPreference.getStringData(SharedPreference.USER_ID)
    if (BuildConfig.DEBUG) {
        val interceptor = HttpLoggingInterceptor()
        interceptor.setLevel(HttpLoggingInterceptor.Level.HEADERS)
        interceptor.setLevel(HttpLoggingInterceptor.Level.BODY)
        okhttpClient.addInterceptor(interceptor)
        okhttpClient.addInterceptor(Interceptor { chain ->
            val response = chain.proceed(chain.request())
            if (!response.isSuccessful) {
                when (response.code) {
                    CommonUtils.ALREADY_LOGGED_IN -> {
                        
                        sharedPreference.setBoolean(SharedPreference.IS_LOGGED_IN, false)
                        sharedPreference.clear()
                        context.getCacheDir().delete()
                        val intent = Intent(context, LoginActivity::class.java)
                        intent.addFlags(Intent.FLAG_ACTIVITY_CLEAR_TASK or Intent.FLAG_ACTIVITY_NEW_TASK)
                        context.startActivity(intent)
                    }
                }
            }
            response
        })
    }

    okhttpClient.addInterceptor(Interceptor { chain: Interceptor.Chain ->
        val builder1 = chain.request().newBuilder()
        var request: Request? = null
        if (!token.isEmpty()) {
            builder1.addHeader("auth_key", "" + token)
        }
        if (!user_id.isEmpty()) {
            builder1.addHeader("user_id", "" + user_id)
        }
        request = builder1.build()
        chain.proceed(request)
    })
    return okhttpClient.build()
}

@Provides
fun providesGSONConvertorFactory(): Converter.Factory {

    return GsonConverterFactory.create()
}

@Provides
fun providesRetrofit(baseUrl: String, convertor: Converter.Factory, okHttpClient: OkHttpClient): Retrofit {
    return Retrofit.Builder().baseUrl(baseUrl).addConverterFactory(convertor).client(okHttpClient).build()
}


@Provides
fun providesApiService(retrofit: Retrofit): ApiService {
    return retrofit.create(ApiService::class.java)
}
}

单例实例在 hilt-dagger 中创建一次，但登录后令牌和 user_id 将可用。登录后，我将需要新的 okhttpclient。我在没有 DI 的情况下做到了。但不知道如何处理hilt-dagger。

阿南德

更好的方法是为@Headers("Token-required")需要令牌的 API注释您的 API 服务方法。然后在您的拦截器方法中检查此标头为：

if (request.header("Token-required") != null) {
        request = request.newBuilder()
            .addHeader("token", "your token value")
            .build()
}

本文收集自互联网，转载请注明来源。

如有侵权，请联系 [email protected] 删除。