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
I've used Syntastic for a while and just stumbled across validator when browsing this issue vim-syntastic/syntastic#699
The conclusion there seemed to be that it's not feasible to allow syntastic to run the validations in a remote environment, at least partly because it sounds like syntastic checks can only run synchronously.
I noticed that validator mentions being an asynchronous validation checker, so I'm curious, is it possible to run validations in a remote environment? For example, ssh to a build server or docker exec into a running container
For some kinds of checkers (particularly ones that are more like compilers such as validating flow types in js) setting up the environment can be non-trivial. So it would be really useful to be able to run the checker in my already-configured app or build environment rather than having to separately configure a part of the build environment on OSX where vim is running.
The text was updated successfully, but these errors were encountered:
I've used Syntastic for a while and just stumbled across validator when browsing this issue vim-syntastic/syntastic#699
The conclusion there seemed to be that it's not feasible to allow syntastic to run the validations in a remote environment, at least partly because it sounds like syntastic checks can only run synchronously.
I noticed that validator mentions being an asynchronous validation checker, so I'm curious, is it possible to run validations in a remote environment? For example, ssh to a build server or
docker exec
into a running containerFor some kinds of checkers (particularly ones that are more like compilers such as validating flow types in js) setting up the environment can be non-trivial. So it would be really useful to be able to run the checker in my already-configured app or build environment rather than having to separately configure a part of the build environment on OSX where vim is running.
The text was updated successfully, but these errors were encountered: