Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project Organization By Feature vs. Watch.Javascripts #393

Open
kenblood opened this issue May 26, 2014 · 2 comments
Open

Project Organization By Feature vs. Watch.Javascripts #393

kenblood opened this issue May 26, 2014 · 2 comments

Comments

@kenblood
Copy link

As much as I like the concepts and implementation of Mimosa, I may have run into a problem. I'm committed to organizing project directories by feature/function instead of file types. I believe that it reduces a lot of long term development friction and difficulty.

However, it appears that Watch.Javascripts (for example) can't accept an array of directories, but only a single string. I have .js files in subdirectories under projectroot/src/app/ as well as subdirectories under projectroot/src/common. Is there a way to accomodate the "by feature" setup now, or any future hope for same?

@Anachron
Copy link
Contributor

I've been waiting for this for ages. 👍
This will require a big refactoring through!

@dbashford
Copy link
Owner

Yeah, this is a tough one.

Accepting multiple is pretty much a non-starter. I really can't even fathom how difficult that would be.

Ideally, there's no need for a javascriptDir at all. That's the better target. I have a bunch of travel ahead of me and hope to knock out some other small things that have built up, but I can take another look after that.

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

No branches or pull requests

3 participants