A modern programming language that makes developers happier.

kotlinlang

I'm still pretty new to dagger, but I was using multi bindings @IntoSet on my @Provides methods that provide something called `Interceptors` from okhttp library. The thing is that interceptor order matters, and so now I believe that I need to move away from IntoSet into something that allows me to dictate order. Am I missing some other api like @IntoList or something or does this basically mean that I can't/shouldn't use multi bindings for interceptors?

well, you could use `@IntoMap @IntKey(1)` etc. for ordering, but I don't think it's a great fit

e.g. in addition to order, you have to distinguish application interceptors and network interceptors separate despite them being the same type

Ordering is unfortunate IMO. One solution would be to provide your custom wrapper like `data class OrderedInterceptor(val order: Int, val interceptor: Interceptor)` and inject `Set&lt;OrderedInterceptor&gt;`. Then you can provide those with orders e.g. in the range of 0-100, and when adding them to `OkHttp` do `orderedInterceptors.sortedBy { it.order }.forEach { builder.addInterceptor(it.interceptor }`

what i do is have a `Set&lt;Interceptor&gt;` for those that don’t care for ordering. Then for those that do matter on ordering. us an interface.

```interface HttpClientConfigVisitor {

    /**
     * Override to influence visitation ordering.
     * Sorting is done in descending order.
     *
     * Some elements like logging needs to be last in the list so that
     * any request mutation happens before the first log entry is created.
     * This should ensure the correct request information is logged.
     */
    val affinity: Int
        get() = Int.MAX_VALUE

    fun OkHttpClient.Builder.visit()
}```

then you need only implement the visitor interface to gather up and run the interceptors