You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 13, 2018. It is now read-only.
A lot of linting plugins, but more specifically ESlint, do not work on remote projects.
Expected Behavior
Linting integration on a project level when working on files remotely via nuclide + watchman
Actual Behavior
Linters like ESlint aren't very useful operating on only the currently opened file, which are evidently all linter plugins in atom have access to when the filesystem is remote.
Here's a follow up discussion about why linter-eslint specifically doesn't work on remote projects AtomLinter/linter-eslint#1017
Can this sort of issue be remedied in some trivial way, given the SSH connection and all of the Nuclide/flow capabilities?
Unfortunately, there is no straightforward remedy short of bundling an ESLint server into the Nuclide server. @wanderley is currently working on it - we should hopefully be able to open source this at some point :)
Knowing that something is in the works is very good to know! ESlint is sorely missed in these remote projects, maybe this is a good architecture question for the atom crowd.
I'm not sure why this was closed. This is still an issue. Having a solution in the works isn't the same as having a solution. This problem still pains me on a daily basis. :(
I totally feel your pain. I closed the issue because ESlint is its own organization, it's ultimately up to them or create their own ide language server like Facebook has with flow.
I don't know of a more universal solution that Nuclide could facilitate. Running any linter on the remote box and reporting back the results via atom UI doesn't feel very vender agnostic
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue and Steps to Reproduce
A lot of linting plugins, but more specifically ESlint, do not work on remote projects.
Expected Behavior
Linting integration on a project level when working on files remotely via nuclide + watchman
Actual Behavior
Linters like ESlint aren't very useful operating on only the currently opened file, which are evidently all linter plugins in atom have access to when the filesystem is remote.
Here's a follow up discussion about why linter-eslint specifically doesn't work on remote projects AtomLinter/linter-eslint#1017
Can this sort of issue be remedied in some trivial way, given the SSH connection and all of the Nuclide/flow capabilities?
Versions
Additional Details
apm ls --installed
):The text was updated successfully, but these errors were encountered: