disable analysis

[tim.webster]

Hi,

Is there any way to temporarily disable SonarLint for IntelliJ without deactivating the plugin and restarting?  I can't seem to find one.

This is useful when you are constantly changing a lot of files at once - the constant analysis makes the IDE jerky and unresponsive.  A simple 'disable' button in the SonarLint tool window would be nice.

Thanks..

[Julien HENRY]

Hi Tim,

I don't think there is a way currently. You know our goal is to make SonarLint "configuration free" so we will try to avoid adding such manual option at all cost.

Could you precise the exact steps to reproduce the issue (sorry, I'm not an IntelliJ user)? For example does it occurs when you do a refactoring, or a big "search / replace"? Maybe we could automatically disable SonarLint analysis in the offending situation.

++

Julien

--
You received this message because you are subscribed to the Google Groups "SonarLint" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sonarlint+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sonarlint/fb8f3ae7-97af-4d7e-a661-fd5bfeef0155%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Tim Webster]

Hi Julien,

Yes - I'm doing exactly that kind of stuff right now (search and replace, and moving files).  Also I have an decent PC with an SSD, so if someone had a hard disk it would be even worse.

I understand the need for less configuration (I'm guessing/hoping most would come from the server?), but if you turned if off for these tasks when would it be turned back on for these files?  When you viewed them again?

This has some implications obviously...

Cheers,

Tim

[Julien HENRY]

I have created this ticket and we will investigate more deeply during next sprint:

https://jira.sonarsource.com/browse/SLI-89

Thanks for the feedback.

Le mardi 31 mai 2016 14:37:05 UTC+2, tim.webster a écrit :

Hi Julien,

Yes - I'm doing exactly that kind of stuff right now (search and replace, and moving files).  Also I have an decent PC with an SSD, so if someone had a hard disk it would be even worse.

I understand the need for less configuration (I'm guessing/hoping most would come from the server?), but if you turned if off for these tasks when would it be turned back on for these files?  When you viewed them again?

This has some implications obviously...

Cheers,

Tim

On Tue, May 31, 2016 at 1:12 PM, Julien HENRY <julien...@sonarsource.com> wrote:

Hi Tim,

I don't think there is a way currently. You know our goal is to make SonarLint "configuration free" so we will try to avoid adding such manual option at all cost.

Could you precise the exact steps to reproduce the issue (sorry, I'm not an IntelliJ user)? For example does it occurs when you do a refactoring, or a big "search / replace"? Maybe we could automatically disable SonarLint analysis in the offending situation.

++

Julien

2016-05-31 13:51 GMT+02:00 tim.webster <tim.w...@gmail.com>:

Hi,

Is there any way to temporarily disable SonarLint for IntelliJ without deactivating the plugin and restarting?  I can't seem to find one.

This is useful when you are constantly changing a lot of files at once - the constant analysis makes the IDE jerky and unresponsive.  A simple 'disable' button in the SonarLint tool window would be nice.

Thanks..

--
You received this message because you are subscribed to the Google Groups "SonarLint" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sonarlint+unsubscribe@googlegroups.com.

[Tim Webster]

OK thanks.

I'll just mention a couple of other things that hopefully you can keep in mind..

 - in IntelliJ, you have the option of disabling any inspection.  It's a bit inconsistent if you can't disable SonarLint.  There was one other scenario where I wished I could turn it off, and it was a new side-project that wasn't bound to the server.  There was no reason for SonarLint to be running and I just wanted to turn it off.

- Also in IntelliJ, when you check in you have the option to 'Perform code analysis' before committing (it's a check-box on the commit dialogue).  If for some reason the analysis was turned off (for example if you implement your proposed functionality), it would be useful for this 'Perform code analysis' to trigger SonarLint on the files in the changelist.

Thanks,

Tim

On Tue, May 31, 2016 at 2:10 PM, Julien HENRY <julien...@sonarsource.com> wrote:

I have created this ticket and we will investigate more deeply during next sprint:

https://jira.sonarsource.com/browse/SLI-89

Thanks for the feedback.

Le mardi 31 mai 2016 14:37:05 UTC+2, tim.webster a écrit :

Hi Julien,

Yes - I'm doing exactly that kind of stuff right now (search and replace, and moving files).  Also I have an decent PC with an SSD, so if someone had a hard disk it would be even worse.

I understand the need for less configuration (I'm guessing/hoping most would come from the server?), but if you turned if off for these tasks when would it be turned back on for these files?  When you viewed them again?

This has some implications obviously...

Cheers,

Tim

On Tue, May 31, 2016 at 1:12 PM, Julien HENRY <julien...@sonarsource.com> wrote:

Hi Tim,

I don't think there is a way currently. You know our goal is to make SonarLint "configuration free" so we will try to avoid adding such manual option at all cost.

Could you precise the exact steps to reproduce the issue (sorry, I'm not an IntelliJ user)? For example does it occurs when you do a refactoring, or a big "search / replace"? Maybe we could automatically disable SonarLint analysis in the offending situation.

++

Julien

2016-05-31 13:51 GMT+02:00 tim.webster <tim.w...@gmail.com>:

Hi,

Is there any way to temporarily disable SonarLint for IntelliJ without deactivating the plugin and restarting?  I can't seem to find one.

This is useful when you are constantly changing a lot of files at once - the constant analysis makes the IDE jerky and unresponsive.  A simple 'disable' button in the SonarLint tool window would be nice.

Thanks..

--
You received this message because you are subscribed to the Google Groups "SonarLint" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sonarlint+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/sonarlint/fb8f3ae7-97af-4d7e-a661-fd5bfeef0155%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "SonarLint" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sonarlint+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/sonarlint/3016f318-2f83-402c-afa9-726606c9851c%40googlegroups.com.

[linck.ken]

I would vote up on this.  Real time is a great goal but often its at the expense of something else.  The moment you decided to disable it anyway for certain situations as suggested, it would seem your already needing to build this concept in anyway.  Why not expose this feature and allow developer to decide?  Its a pay now or pay later decision right?

Would be nice to keep the plugin more flexible for those that would like to utilize it at a pre-commit event on changed files once per file than everytime a file is modified.

Ken

Sent from my T-Mobile 4G LTE Device

To view this discussion on the web visit https://groups.google.com/d/msgid/sonarlint/CABrquLxeU1uUEWRM4kL%3Dmp7uEtXxZwnFRHMJ-CTWnowj2J-txw%40mail.gmail.com.

[cham...@gmail.com]

I also like to vote up this issue. We have large legacy code base and we are not fixing issues if those are not relate some modification that i'm doing. It's a company rule. But for a legacy code like that may have lot of issues. And sometimes it looks messy with lot of issue marks in the notification strip. It's hard to see other marks like usage highlights and etc while coding. So it would be great if i can switch it via short cut time to time. So i can analyze and fix an issue if i've introduced and disable it to continue coding. 

[duarte.meneses]

We plan to add the following features which should help:

* Support exclusion of files from the analysis, so that legacy files can be excluded (https://jira.sonarsource.com/browse/SLI-72)

* Don't show issues that are marked as resolved in SonarQube (https://jira.sonarsource.com/browse/SLI-83)

Currently, as a work around, it is possible to disable the automatic trigger of analysis in the SonarLint General Settings, which is more reasonable than to temporarily disable the plugin.