mrcljx / rubocop-for-rubymine

DEPRECATED: RubyMine supports RuboCop now
https://blog.jetbrains.com/ruby/2017/01/rubymine-2017-1-eap-2-creating-gemsets-rubocop-support/
MIT License
131 stars 29 forks source link

Any way to stop the repeated missing RuboCop gem warning? #12

Closed justin808 closed 9 years ago

justin808 commented 9 years ago

This is caused when I switch to projects not using rubocop as my settings for RubyMine for RuboCop are not project specific.

linters_rake_-_investor-dashboard_-____clients_madrone_investor-dashboard__and_gemfile_-_rebar_-____railsonmaui_rebar_

justin808 commented 9 years ago

BTW, thanks for the awesome plugin!

mrcljx commented 9 years ago

This is interesting. https://github.com/sirlantis/rubocop-for-rubymine/blob/5e3670677e0ab8462bb29e404ad120d661e3155c/src/io/github/sirlantis/rubymine/rubocop/RubocopTask.kt#L50-L53 should check, whether the project has a .rubocop.yml before running any Ruby code (which will then trigger those warnings).

Do those projects have a .rubocop.yml?

justin808 commented 9 years ago

Make an error in any rake task (say while editing one, save it as invalid) and the plugin goes berserk.

mbasset commented 9 years ago

I also have this same issue. It tends to happen when the Gemfile is updated or ruby version changed or rubocop gem is not installed.

levilansing commented 9 years ago

+1 I love the plugin but this error message drives me crazy every time I change my Gemfile, especially if I run into dependency issues because the errors just keep piling up until bundle install succeeds. Is there any way we could get just one error that is much smaller so it doesn't cover half the editor? Ideally it would go away once the problem is solved as well!

Yesterday I had to click the little x about 30 times :/

mrcljx commented 9 years ago

I've changed this now to kill previous messages of the same time. So you should only see one of those messages appear.

levilansing commented 9 years ago

wonderful! thanks!