Is it safe to call `decodeString ` and then if it throws an kotlinlang #serialization

Is it safe to call `decodeString()` and then if it...

# serialization

c

CLOVIS

10/31/2025, 4:27 PM

Is it safe to call

decodeString()

and then if it throws an exception attempt to

decodeXXX()

again? I have some data that is sometimes encoded in a String.

e

ephemient

10/31/2025, 4:41 PM

not across formats, no

c

CLOVIS

10/31/2025, 4:41 PM

Ok. Is it safe for JSON?

e

ephemient

10/31/2025, 4:41 PM

for JSON specifically, decodeJsonElement and then determine if you want to treat it as a String or not

👀 1

🙏 1

➕ 1

c

CLOVIS

10/31/2025, 4:42 PM

How would go around deserializing some data across formats that is sometimes encoded slightly differently? (and there is no way to tell other than looking at it)

e

ephemient

10/31/2025, 4:42 PM

unfortunately I think it's going to be format-dependent because not all formats will support that

➕ 1

c

CLOVIS

10/31/2025, 4:42 PM

I see. Thanks!

e

ephemient

10/31/2025, 4:49 PM

actually I guess it's only JSON format which has support now, other formats which could support it, currently don't https://github.com/Kotlin/kotlinx.serialization/issues/1573

➕ 1

c

CLOVIS

10/31/2025, 4:50 PM

I am planning to support that in my own BSON format, we'll see what happens

CLOVIS

10/31/2025, 4:58 PM

But mine goes a bit further, it doesn't parse the sub-thing at all until the user explicitly asks for a specific field

2 Views