Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

Support for multiple project directories #6

Open
cdata opened this issue Oct 2, 2016 · 6 comments
Open

Support for multiple project directories #6

cdata opened this issue Oct 2, 2016 · 6 comments

Comments

@cdata
Copy link

cdata commented Oct 2, 2016

As an Atom editor user,
when I open multiple project folders at once,
I want my code to continue to be linted,
so that I can be a productive software engineer

Currently, when more than one project folder is opened, I receive an error that says that the Polymer linter will only work with projects that have exactly one root directory. However, it is a fairly common work flow within Atom to open multiple project directories to make switching contexts easier to do. It would be nice if the Polymer linter continued to work in these conditions.

image

@cdata
Copy link
Author

cdata commented Oct 2, 2016

Also, it's kind of annoying that the error persists the way it does. I don't want to have to toggle off linting just to dismiss it :P

@notwaldorf
Copy link

Also related: #3

@TimvdLippe
Copy link
Contributor

@rictic Hitting this too right now while developing on both the analyzer and editor-service. What is the underlying reason for reporting this error?

@rictic
Copy link
Contributor

rictic commented Nov 21, 2016

Oh, yeah, we shouldn't report it in a persistent way, just as a popup.

The underlying reason is just so that people aren't surprised when none of the IDE features work.

@TimvdLippe
Copy link
Contributor

when none of the IDE features work

Okay but could we work around this; e.g. what is the issue we need to fix? Would like to fix this one for my own development workflow too 😄

@rictic
Copy link
Contributor

rictic commented Nov 21, 2016

I think we'll need one editor server per workspace. Which is fine if you've got, say, 2-5 workspaces. If you've got, like 100 workspaces (not naming names here or anything but such people do exist), and each of those workspaces has its own dependencies, then RAM usage could get kinda crazy high.

Hm. On the other hand, if we only instantiated an editor service when a workspace is first modified then everything would probably work out fine. If we also killed idle editor services, it would almost definitely work out fine.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants