by default everything get

toString()

called on it

But how does retrofit serialize path arugments?

toString

But if its the body it uses the converter?

yep

What is the reasoning behind that? I just realized that my

LocalDate

parameters only work by accident ^^

well urls are strings

request bodies are binary

i mean ultimately it's all binary, but urls are always strings

All right, thanks. Even though I would love it to throw an exception if it isn’t a primitive

Good morning guys, I'm having this error on the iOS build since I have started using SQLDelight. I think it's because of when I added the classpath to the project build.gradle file, it asked me to remove the version of kotlin-multiplatform on the plugins task in the lib build.gradle. Maybe there are conflicting libraries?

What's the reasoning for making SQLDelight models interfaces with data class implementations rather than just making them data classes in the first place?

theres an issue somewhere to remove the interfaces

they're not needed anymore

it was a legacy reason to support autovalue

is there a way to make the generated model classes implement an interface without wrapping it? Or it that just really gross practice

wrapping it is the only way

Not totally specific to Square libraries, but I'm using Retrofit to make a request (duh) and sending a model that has several

Expose(serialized = false)

annotations. I know this is a Gson thing and not a retrofit thing, but I'm noticing that Gson is still serializing the values that I have annotated NOT to serialize. What's the deal? Posting some code samples in a sec

Model

data class Listing(

    @Expose @SerializedName("brand") var brand: String?,
    @Expose(serialize = false) @SerializedName("id") var id: String?,
    @Expose(serialize = false) @SerializedName("creator_id") var creatorId: String?,
    @Expose(serialize = false) @SerializedName("lowest_price_at") var lowestPriceAt: String?)

Client code

class Client {

    private var rfBuilder = Retrofit.Builder()
    private var service: ClientService

    init {
        this.rfBuilder.apply {
            baseUrl(BASE_URL)
            addConverterFactory(
                GsonConverterFactory.create(
                    GsonBuilder().apply {
                        excludeFieldsWithoutExposeAnnotation()
                        setPrettyPrinting()
                    }.create()
                )
            )
            client(
                OkHttpClient.Builder().apply {
                    addInterceptor { chain ->
                        val original = chain.request()

                        val requestBuilder = original.newBuilder().addHeader("User-Agent", USER_AGENT)
                        val request = requestBuilder.build()
                        chain.proceed(request)
                    }
                }.build()
            )
        }

        <http://logger.info|logger.info> { "Client running with user agent $USER_AGENT" }
        this.service = rfBuilder.build().create()
    }

And then I have a function in that client class that just takes a Listing object and calls

Gson().toJson(listing)

with it and prints it out

What I see is that ALL the fields get serialized, when only

brand

should be serialized

Also... if there is a more elegant way I can write that

init

... I'm all ears 😆 I sorta really love

apply

is it a good practice to have multiple interceptors and each of them takes care of something else. for example HeaderInterceptor adds headers to every request, ExceptionInterceptor checks if request has been made without any exceptions or CodeInterceptor checks what status code has server returned and just do

.addInterceptor(HeaderInterceptor())

to OkHttpClient Builder

I feel like this could easily break SRP, since your

HeaderInterceptor

would need to know about all headers for all endpoints

I think a better way is to have functionality-specific interceptors, e.g. you’d have an

AuthenticationInterceptor

that adds necessary auth headers, or a

LogoutInterceptor

that handles 401 status code and clears local data

if i have two retrofit instances, should i share Interceptors between them ?

it's not a huge savings

you might want to consider sharing the OkHttpClient instance though