Hello, I'm experiencing some issues with Ktor serv...

# ktor

[James]

Hello, I'm experiencing some issues with Ktor server & client when it comes to serializing and deserializing (all serializers). When the type to be serialized or deserialized is String Ktor does not serialize or deserialize it, not on the server side or the client side. I've had to add helper methods to send and accept JSON:

[Aleksei Tirman [JB]]

That's an intended behavior until Ktor 3.0.0. You can make objects of the String type serializable and deserializable in the same way as for other objects by removing it from the ignored types:

install(ContentNegotiation) {
    removeIgnoredType(String::class)
}

[James]

I understand! Thank you! Is there an issue for this I can reference to for documentation?

[Aleksei Tirman [JB]]

Here https://youtrack.jetbrains.com/issue/KTOR-5866

[James]

Thank you very much ❤️

[James]

The workaround does not seem to work when returning a response from ktor-server

[Aleksei Tirman [JB]]

What method do you call to respond?

[James]

call.respondNullable

[James]

I am unable to change this because the part of the application that responds is controlled by an internal web framework that builds on top of Ktor

[James]

This is the respondNullable with the workaround applied

[Aleksei Tirman [JB]]

Unfortunately, I cannot reproduce your problem with respondNullable or respond

[Aleksei Tirman [JB]]

Can you try that on a sample project?

[James]

I apologize! This is my bad!

[James]

There are three different locations where this should've been applied for us, it was only applied on two of them which was in testing modules and not in the actual ktor part of the module!

[James]

It almost works as expected, I'm having some issues with external modules, please let me double check to see if the changes was applied there too

[James]

Nevermind, it is with the test client. Give me a moment to try and figure that one out

[James]

Great! Everything is working as expected! There was one undocumented #wtf-ktor left. It has been set to use the workaround now!

[James]

Thank you Aleksei!