Preview mode is gone. How to report issues without committing them to database?

[ganncamp (G Ann Campbell)]

Hi,

There’s a lot here & some of your points intertwine IMO, so forgive me if this gets confused…

@tbutler

a) because the engineers want a command line tool

Even more than they want to stay in-context in the IDE? I would expect a CLI to be a second-best, at best.

@tbutler

pull in linting results and get a quick idea if their code quality is good.
Yes you can have IDE plugins for linting tools but that doesn’t help with point a) and also means you don’t have a “single source of truth” - ie the SonarQube analysis - for all of the issues,

Okay… SonarQube is the single source of truth.

SonarLint is a first line of defense - the first few, actually. By default it’s going to tell you what pops up in your code as you type. That’s the first line. Second line (in SonarLint for IntelliJ/JetBrains): there’s a pre-commit view where you can see all the issues in the files you’ve changed, before you commit them.

That’s explicitly designed to help developers “get a quick idea if their code quality is good.”

@tbutler

I do recognise that this is imperfect - if nothing else because it does not include code coverage

To be clear, it also doesn’t include duplications, and certain categories of rules.

 
HTH,
Ann