Missing useful error popups on 6.0.3

In previous versions I used to get useful error popups when I hovered over the wavy-line error markers. Sometimes they would be really helpful - I actually learned a lot about the language from them. In this version the only error I ever get is the one about double quotes around a string with no interpolation.

Ironically, this is the only one I would like NOT to see - as the coding styles we use here are based on the Github styles, which state that double quotes should always be used.

So:

How do I switch on the other errors pop-ups?

How do I switch off the double quotes error?


Thanks!

12 comments
Comment actions Permalink

Hi,

we have not changed default settings and you are supposed all warning you've seen earlier
unless you have disabled all inspectsions at once.  Go to Settings|Inspections and check which
incpections are enabled in yur ide now.   There you can enable/disable any of our inspection (including the one about double-quotes ;)

Hope this helps, Oleg.

0
Comment actions Permalink

I had a look through inspections and I was able to turn the string inspections off. A lot of the inspections are working, however I still get words marked as problematic (white/grey/cream squiggly line) that don't give me a pop-up.

I would assume that if they are so marked, they should be turned on in inspections and I should get a pop-up.

Is there a circumstance where I should get marked text and no pop-ups?

In the meantime, I'll try turning inspections on and off to see if I can work out which ones are causing a problem.

B

0
Comment actions Permalink

Well, every time we highlight something we are supposed to give more information.
Could you please provide some screenshot which will demonstrate the problem.

Regards, Oleg.

0
Comment actions Permalink

When I'm out of these interminable meetings and back in front of some code I'll try and get some more information.

0
Comment actions Permalink

The offender is 'unresolved Ruby reference'.

An example of where I'm seeing it is:


require 'spec_helper'

describe SomeController do

    describe "GET #index" do

        before(:each) do
            10.times { create(:some_object) }

            get :index, :use_route => ""
        end

        it "responds with 200" do
            expect(response).to be_success
            expect(response.status).to eq 200
        end
...

It appeared on 'spec_helper' in the require and the be_success expectation itself.

In both cases rollover does nothing. Switching off the inspection clears them both. The code is working, so the references obviously exist.

The only real oddity about this project is that the root folder contains three Rails projects, one an engine.

Other than that I'm on a Macbook Pro, OSX 10.8.

Any ideas?

0
Comment actions Permalink

RubyMine is unable to find spec_helper, most likely because of "unexpected" structure.of the project.
It does't know where to find this file (I suspect it is not located in the same directory as the spec ;)
Why do you use such a strange project structure?  Perhaps it would be better to have separate projects for every rails project and for the rails engine.

Oleg.

0
Comment actions Permalink

The problem is that rolling over the error is not giving me the reason for it. Whether you agree with the project structure isn't really an issue... ;)

The reason is mainly to avoid having to work with 4 different Rubymine windows. (One each for the webapps, one for the engine and one for the root folder...) Unless there's a way to get multiple projects in the same window that snuck in while I wasn't looking....

B

0
Comment actions Permalink

However, I've had to turn off the offending inspection as it was driving me nuts.

0
Comment actions Permalink

That's massive news! And a very cool feature.

Thanks for pointing that out. I've now set the Rails project in question to be a single Rubymine project and things are much easier to use.

However, the original bug still remains:

Rolling over 'be_success' in the included image has no effect. Again, it's switched off by switching off the 'unresolved Ruby reference' inspection.

Any idea why that inspection is failing?



Attachment(s):
inspection.tiff
0
Comment actions Permalink

Hi,

most likely the problem is in RubyMine :(  be_* matchers require additional type information and we supposed to get it automatically but it looks like not always :(
Is it possible to provide  a test project which demonstrate the problem? If so could you please file a ticket in our tracker(http://youtrack.jetbrains.com/issues/RUBY) about it.

Regards, Oleg.

0
Comment actions Permalink

It's not just that file. I was getting these phantom errors before there was even a single test added to the code.

I'll try to get time to set up a project to isolate the error without pasting up too much production code.

0

Please sign in to leave a comment.