Closed benadamstyles closed 6 years ago
Hey thanks for the feedback I appreciate it! I figured this would be the case while building it, and have two fixes in mind to improve performance on larger projects:
1) is a great idea.
2) haha yes I think you're right. Can't think of an example where specifying excludes rather than includes would be better. If there's any way I can help, let me know.
Hey man, just published an update implementing #2 from above. Thought through the first idea and it actually causes some correctness issues when extended to the case where styles and defined in multiple directories so I'm going to save that one for a bit later. Let me know if specifying the style directory alone speeds things up on your larger projects!
Hey, thanks. Forgive me for being thick, but how should I be referencing the path? My file structure is:
- app
- common
- stylesheets
I've tried app/common/stylesheets
, app/common/stylesheets/
, ./app/common/stylesheets
...
Its an absolute path for now! So gotta do the full thing like /Users/MyName/Documents/code/project/styles...
Let me know if this improves performance at all for you!
Hey, sorry for the delay – it works a treat yep. However, it's probably not a final solution because every time you work on a different project (I have like 8 on the go at the moment!) you have to change the path. The only solution i can think of off the top of my head is to require an optional json file in each project's root that can hold the path. .atomqe
or something.
Hey, love this package, thanks so much for building it!
It runs quite slow in some of my larger projects. Do you think this could be because
atom.workspace.scan
searches all directories? If so, it would be great to have a config setting to exclude some directories, because for example I'm never going to want it to searchnode_modules
.