Atom-ide-ui: Please coordinate with Atom-Linter

Created on 26 Oct 2017  路  6Comments  路  Source: facebookarchive/atom-ide-ui

It would be nice if these two projects could coordinate with one another in a better way. Your addon takes the assumption that it's the one stop shop for everything when in-fact, it's not. There is no proper ide-ruby so I must use atom-linter, but when I have your addon enabled, you complain, about linter, so I have to manually disable your addon just to work with Ruby files.

It would be nice if your two addons could coordinate with each other, either you use linter, or your debugger coordinate with the linter to disable it automatically if you find no supported ide-package

Most helpful comment

I feel like this can be closed...

All of us involved have worked very hard to make sure Linter packages work with atom-ide-ui and that Atom IDE works with linter-* providers. So much so that all diagnostics providing ide-* packages are listed on the AtomLinter package list.

All 6 comments

On another note: I doubt there will ever be a proper ide-ruby unless the author of the server for Ruby decides to stop being insane about having to use Docker to use his server, or somebody builds something that's less insane and more flexible and speedy because launching Docker is expensive so expecting it to use a server for a language is a terrible idea.

Just to note, linter-rubocop _should_ work with atom-ide-ui as it uses the same service API that linter itself does... other than https://github.com/AtomLinter/linter-rubocop/issues/248 apparently which you should file here. (I'm guessing they are only checking lintOnFly, not lintsOnChange as well.)

I _think_ what might be causing you issues is that currently most of the linter-* providers require linter to be _installed_, but shouldn't require it to be enabled so if you prefer atom-ide-ui's interface to messages you can leave linter disabled.

The two packages can co-exist just fine, it's just that you either have to disable Diagnostics or you have to disable Linter (to avoid duplicated errors and warnings).

You should have gotten a notification similar to the one in https://github.com/facebook-atom/atom-ide-ui/pull/25 right? With an option to disable one of them? That's all you have to do :)

I have this funny feeling a lot of the problem was configuration confusion. Atom-IDE-UI doesn't necessarily make the configuration unconfusing and I had to dig through all the settings to get rubocop linter to run the way I wanted without having to disable atom-ide-ui but still using linters.

@envygeeks Does the above discussion resolve your issues? If not, what needs to be done here? (@AtomLinter org owner here...)

I feel like this can be closed...

All of us involved have worked very hard to make sure Linter packages work with atom-ide-ui and that Atom IDE works with linter-* providers. So much so that all diagnostics providing ide-* packages are listed on the AtomLinter package list.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

niccolomineo picture niccolomineo  路  6Comments

tiagonervis picture tiagonervis  路  4Comments

richiksc picture richiksc  路  3Comments

fenric picture fenric  路  3Comments

danielalmeidagoncalves picture danielalmeidagoncalves  路  8Comments