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
Every change of every file in my project's directory notifies solargraph of a file-change and causes a new indexing-process.
So in my rails-projects every page-reload triggers a lot of reindexing-processes, because a lot of files change while handling the request (multiple changes in log-file, cache-files etc.). This slows atom down to be unusable.
I created a .solargraph.yml in the project's directory, but this seems to be ignored.
I'm using rbenv for managing ruby-versions.
The text was updated successfully, but these errors were encountered:
The language server depends on the client to monitor the filesystem and report changes to watched files. In VS Code, the client can minimize server notifications with a filter on the filesystem watcher. I'm not sure if there's a similar mechanism in Atom. I'll have to research it.
Switching the "File System Watcher" from "Native operating system APIs" to "Experimental filesystem watching library" in the core-settings seems to do the trick.
Every change of every file in my project's directory notifies solargraph of a file-change and causes a new indexing-process.
So in my rails-projects every page-reload triggers a lot of reindexing-processes, because a lot of files change while handling the request (multiple changes in log-file, cache-files etc.). This slows atom down to be unusable.
I created a .solargraph.yml in the project's directory, but this seems to be ignored.
I'm using rbenv for managing ruby-versions.
The text was updated successfully, but these errors were encountered: