Marc Knaup

Just ran into the same error: ```kt import kotlinx.serialization.* import Test.* @Serializable class Test(val bar: Bar) { companion object @Serializable class Bar(val value: Int) } ``` ```text org.jetbrains.kotlin.util.KotlinFrontEndException: Front-end Internal...

Same for me. The server adds computed properties to certain data classes to have their logic server-side instead of client-side.

I've just started using kotlinx-serialization in a new project and this is basically the first issue I came across, with a compiler error that's not very helpful (location: "File is...

Ouch, this also got me after upgrading to Insomnia 8. For me so far, it only happens when the GraphQL request is triggered by a placeholder/reference in another request (non-GraphQL...

Workflows with request references are still broken completely for me due to this. Also in the latest version 8.6.1.

In the meantime, I've [created a fork](https://github.com/fluidsonic/chrome-devtools-java-client) and released it on Maven Central under `io.fluidsonic.mirror:cdt-java-client:4.0.0-fluidsonic-1`. This PR is the only change.

Setting `remote-allow-origins` to `*` by default likely defeats the security purpose for which it was introduced. Explicitly setting it makes more sense for now as it highlights a potential security...

Thanks, that weird surrogate hack indeed works for `String` :) Just not really nice nor efficient. It also would be even better if ```json {"type":"OkResponse","data":{"type":"String","value":"good"}} ``` would become ```json {"type":"OkResponse","data":"good"}...

I think so. I don't have the server anymore where I had that issue so I cannot test anymore.

@segiddins Working with Development Pods isn't fun and Xcode is more than capable of building modular apps consisting of many frameworks. Why should I make that more complicated with CocoaPods?...