Feel like I'm hitting a bug. Present in 3.0 and 3....

# supabase-kt

[Colton Idle]

Feel like I'm hitting a bug. Present in 3.0 and 3.0-dev1 (didn't try anything else)

io.github.jan.supabase.exceptions.BadRequestRestException: null value in column "type" of relation "config" violates not-null constraint

supabase.from("config").insert(Config())

is the failing code
data class has a hardcoded type field

@Serializable
data class Config(
    val type: String = "abc"
)

but if I keep everything else the same, but change the invocation to have an explicit type

supabase.from("config").insert(Config("xyz"))

then it works.

Seems like supabase-kt doesn't pick up the default value of a data class?

[Jan]

That is because by default, KotlinX Serialization (the default serializer used by supabase-kt) does not encode default values.
You can change this by providing a custom Json instance:

val supabase = createSupabaseClient(url, key) {
    defaultSerializer = KotlinXSerializer(Json { encodeDefaults = true })
}

[Jan]

Too many defaults in one sentence

[Colton Idle]

Interesting! I'm used to moshi and I guess it does the opposite.

Glad it was a quick change. phew