"No editor is available" dialog in IntelliJ Database tab
Issue #1089
resolved
I use IntelliJ to do SQL, Java and Salesforce development. When I am in a project that is SQL only, has never been configured to work with IlluminatedCloud, I get dialog boxes from Illuminated Cloud.
One such example is in the Database tab. Every time I click on a database connection, I get a dialog:
"No editor is available for <database name> Would you like to open <databasename>-meta.xml?"
This has been happening for the last few point releases, but is confirmed in 2.0.3.4.
Is there a way that IlluminatedCloud can be disabled / enabled on a per-project basis?
Somewhat related - preferred-vcs.xml should not be created on projects that do not utilize IlluminatedCloud.
Comments (12)
-
repo owner
-
reporter
Thanks!
-
repo owner
Hey, Dan. Can you give me an example of what exactly you're doing that's resulting in this error? When I right-click on a DB connection in the Database tool window and click Open Console, it opens just fine. I imagine you're doing something different? I just want to reproduce this before I make any changes. Thanks!
-
reporter
Im on OSX, it triggers when I left click on any database connection.
-
repo owner
Hmmmm...okay. And what version of IntelliJ IDEA are you using? I'm on 2018.2.2. Perhaps that's the difference?
-
reporter
2018.2.2 Ultimate
-
repo owner
Okay. I'm spinning a build now that should fix it. I'll post it here for you to verify the fix, and assuming/once it's good I'll issue a new build tomorrow morning.
-
repo owner
- attached IlluminatedCloud2.zip
Dan, please install this build using Preferences>Plugins>Install plugin from disk and let me know if it resolves the issue or not. It should be filtering out all non-IC source files from this logic. Thanks!
-
reporter
That appears to have solved the issue, thank you!
-
repo owner
Wonderful, Dan. Thanks for confirming! Just stay on that build for now and when I put the official build with this fix out, it'll prompt you to update to the official line again automatically. Sorry again for interfering with your non-Salesforce work like that!
-
repo owner
- changed status to resolved
Delivered in 2.0.3.5.
-
repo owner
- removed component
Removing component: IntelliJ IDEA (automated comment)
- Log in to comment
Oh, man. That shouldn't be happening. So sorry about that, Dan. That logic should in fact only kick in for IC projects and really only for files under an IC source root. I'll try to issue a patch no later than tomorrow morning for that, and I can attach it here earlier if it's really getting in the way for you. Sincere apologies!