- When I set my project's Content Root to the actual project root, RubyMine gives me the "Cannot resolve directory" error highlighting in my define statement (see screenshot). The RubyMine 'Navigate to File' works for files in my project root (ie, /Gemfile, etc)
- When I set Content Root to my "/public" subdirectory, the error highlighting goes away (good), but I can no longer use RubyMine's 'Navigate to File' for files in my project root (ie, /Gemfile, etc)
In RubyMine I've tried:
- Resetting the Content Root
- Adding Load Paths
...but I can't seem to come up with a working combination. I'm not sure if I just don't understand how this is supposed to work or what. I want them to all be project files because... 1) they are and 2) to keep the number of file matches down in the 'Navigate to File' dialog.
Any easy solutions? Bugs I should vote for? Add a bug/feature request? All guidance/suggestions appreciated, thanks all - Bruce
Update - verified by JetBrains as a bug. If you care about this, vote for: http://youtrack.jetbrains.com/issue/RUBY-14419