Jens Fischer
Jens Fischer
Something like that, yeah.
The extension changes the default setting of `formatOnSave` for yaml files, which is rather intrusive IMO: https://github.com/longkai/kubernetes-yaml-formatter/blob/ff7108ed65ed84496c085c4e65130d6cce4d9120/package.json#L97-L101
That should work fine with compiler completion? I think intellij-haxe has a setting to enable that.
I think you would have to replace _all_ hardcoded `haxelib` invocations in the compiler - that's not just `haxelib path`, but also `haxelib run hxcpp/hxcs/hxjava`. IIRC @back2dos suggested something like...
Not sure why something named "CI" should imply non-colored output. We specifically use `-Dorg.gradle.console=colored` on CI for improved readability.
> Well, since code path for Map is the same, you're touching it in any case. In particular, this code throws a decoding exception now We ran into one such...
I think that's always been the case - that's what I meant by "restarting VSCode".
It seems like this phase timing output did not exist in that version? However, `gradle detektMain detektTest --continue --debug --rerun-tasks` takes around 4 minutes 30 seconds for the entire multi-module...
Ah, it seems like an explicit `debug = true` is needed in the `detekt {}` block. With v2 the `--debug` was enough IIRC. It looks like the slowest binding phase...
Giving this another try with 2.0.0-alpha.1, at first it looked like things haven't improved at all or even gotten worse (had a bunch of detektMain tasks seemingly not making much...