radarlint plugin documentation?

[ziz]

Question

The radarlint plugin (and its associated plugins) seem to be undocumented. Only a few places have a link for it, and the link goes to https://github.com/qltysh/radarlint which 404s. Can you provide documentation for this plugin, including configuration directives and a dictionary of rules it applies?

How to reproduce (optional)

Expected behavior (optional)

No response

CLI Version

qlty 0.541.0 macos-arm64 (833779b 2025-06-11)

Information about Qlty configuration and environment (optional)

// Add your qlty.toml

• OS:

[daviddening]

@marschattha Any thoughts on this? I'd love to configure radarlint a bit to permit more nesting (our code does quite a bit of functional programming)

radarlint-js:typescript:S2004

[marschattha]

Hey, thanks for bringing attention to this, added a readme on radarlint configuration. https://github.com/qltysh/radarlint/blob/main/config.md

[daviddening]

@marschattha that link 404s. Is the radarlint repo not publicly accessible ?

[marschattha]

Ah sorry about that, it is private right now, we just need to review it and hopefully it will be public by next week.

[daviddening]

@marschattha Curious if there is any update?

[marschattha]

cc: @brynary

[venriq]

???

[scottohara]

Came to ask the same thing.

I have a couple of Java-based projects, and with Java not being one of my stronger programming languages, the issues that radarlint-java raises are difficult to comprehend.

I mean, the one-line descriptions are fine; but usually with most linters each rule is backed by some rationale explaining why something is considered bad practice; and that is what I was hoping to find documented.

For example, "Define and throw a dedicated exception instead of a generic one" makes perfect sense, and I can probably guess what I need to do to fix that one. But some examples and a brief "...and here's why its recommended" would go a long way.

"Add a private constructor to hide the implicit public one" - ok, sure but....why? I'm sure there's a good reason and I bet Claude or one of the other LLMs could help, but someone has decided that this should be a default enabled rule and it would be good to understand the thinking behind that decision.