[haltcatchfire]

I tried to give it a shot this year. Autocomplete (and especially Co-pilot) works really well nowadays. What made me reconsider is actually how imports are sorted and organised - they differ from how IntelliJ does it, which all other developers in my team uses. It’s a tiny but nagging issue for which I haven’t found a solution. It doesn’t help that IntelliJ is spectacularly good out of the box hah…

[soraminazuki]

I always choose standalone tools for formatting so that it can be integrated into any editor/IDE and checked by CI.

[shepherdjerred]

You can run Intellij's checks in CI: https://www.jetbrains.com/qodana/

[mdaniel]

I believe that's _conceptually_ possible but unless you, personally, have actually tried it I wouldn't go so far as to cite that. My hand's on experience was that the thing very easily gets into analysis loops and never terminates. And by "never" I mean that I dialed up the CI timeout to 24 hours just to see if I wasn't patient enough and it still didn't terminate

And that's not even getting into the horror show of trying to view the analysis results of any "hello world" setup wherein it does terminate: a reasonable CI integration would submit those findings as comments on the PR but I had to duct tape one together by transforming the SERIF output into ReviewDog to get that outcome

I am quite possibly the biggest JetBrains fanboy you'll encounter, and was thrilled out of my mind when they announced Qodana, but its execution has been a raging dumpster fire

[shepherdjerred]

I am puzzled that you had such a negative experience. I set this up in the summer and it worked just fine, including comments on PRs. I used https://github.com/JetBrains/qodana-action