Oleg Godovykh

@zach-klippenstein Please take a look at `AddressWorkflow` at internal repo, this is exactly the case of state and output being the same.

Got under my radar completely. Yep, it's a known issue, I've faced it before, but didn't find a way to easily fix it (like in one line). I would say...

Actually, the issue is not only with `testNextRender`, but with chaining a set of calls to `verifyAction` or `verifyActionResult` as well. One idea I have is to cache the result...

The computation results really differs a lot, the same input parameters in our project resolve to zoom level about `14.8` in v10, and `12.1` in v11 — definitely above some...

The non-deprecated `cameraForCoordinates` method from v11.4.0-beta.2 works ok, and resolves the zoom to the same scale as it was for v10

By some coincidence issues like https://github.com/diffplug/spotless/issues/1913 were reproducible for me from time to time with daemon on, and disappeared when I explicitly turned off the daemon. It makes me think...

@Goooler Could your change in #1890 somehow affect how .editorconfig is accessed (or maybe it was always working this way)? I don't see what is triggering `KtlintConfig` recreation, and I...

I have the same issue reproducible in my work project. > it also happens with a completely empty file - contents seem irrelevant In my case it happens only when/if...

> So is that another issue...? That the file cached somewhere, somehow? I've already reported it https://github.com/diffplug/spotless/issues/1924

BTW, I've looked into logs, and it may be an issue on a KtLint API side — it doesn't look like they're properly converting the config value to int (at...