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 believe this is a regression as the issue is not present if I roll back to v0.19.1. It appears as early as v0.19.0-lsp3, and is still present in v0.20.3. So it seems something went wrong somewhere in here: v0.19.1...v0.19.0-lsp3.
For now I'd suggest opening atom at the project root, but ultimately I'd like to at least start multiple language server processes, 1 per project, as the vscode plugin currently does, shouldn't be too hard I think.
Actually I take it back, I don't see a way of making this work without changes to atom-languageclient , as servers are associated with project roots, and I don't think searching subdirectories recursively for a PureScript project is a good idea.
However I think there's a simple workaround (which also makes things a bit more explicit) if you have atom open at a level above your PureScript project: add an additional project folder and move it above the parent in the list:
I believe this is a regression as the issue is not present if I roll back to
v0.19.1
. It appears as early asv0.19.0-lsp3
, and is still present inv0.20.3
. So it seems something went wrong somewhere in here: v0.19.1...v0.19.0-lsp3.Given a directory structure like this:
When I open Atom at
my-project
, I get the following errors:If I open Atom at
my-project/client
, there are no errors and things work as expected.Screenshot
Thanks for the great 📦 !
🥇
The text was updated successfully, but these errors were encountered: