Nicklas Ansman
Nicklas Ansman
Not really, but it can be reproduced using a project with two modules with the main module having this: ``` dependencies { debugCompile project(path: ":submodule", configuration: "debug") releaseCompile project(path: ":submodule",...
Well, releaseCompile might be nice for having different artifacts for debug and release (which is our use case). It would result in two different artifact (one debug and one release)...
```kotlin val request = inputStream.use { app.createRequest(it) } val response = app.handleRequest(request, headers).get() outputStream.use { response.writeTo(it) } ``` That would be the rough outline.
The advantage is to not having to first convert the whole body into a string and then parsing it as JSON. It would save memory and time. This is not...
No exactly, it's a private property that you cannot access and it never written.
Yeah, my bad. I've updated the example
This is likely related to all KSP generated files being missing from `Result.generatedFiles`
I can still not load classes after using `kspWithCompilation = true`. Even with this flag set the class loader till only contains the `classes` dir.
Ah, it turns it it's likely because I'm generating java sources and not kotlin sources. Perhaps this isn't something that KSP/Compile Testing supports?
I would argue that on Android we still want to use `nanoTime` over `elapsedRealtime` as it's more likely that the caller does not want to include time spent in sleep.