So I have a package that, on activation, checks for a special file at the current project root. If that file exists, several components in the package are activated. This ensures that we don’t unnecessarily load code that will never be exercised in the current Atom session.
Right now I’m watching
atom.project to see if it emits a
path-changed event: if it does, I trigger the re-check code.
However, I’m not actually sure what the
path-changed event represents. At the time I implemented the re-check code, I assumed that it was possible for an Atom instance to change its current project directory to something else, but I’ve actually never seen that happen in practice: opening a new project always opens a new Atom instance.
Is my understanding of