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

External options config #102

Open
wearymadness opened this issue Dec 3, 2015 · 2 comments
Open

External options config #102

wearymadness opened this issue Dec 3, 2015 · 2 comments

Comments

@wearymadness
Copy link

I've searched the current open and closed issues so accept my apologies if this has been raised before.

I would like the opportunity to use an external file for the options (think .jshint and/or .scss-lint.yml). I'm working on a project that is going to be distributed to multiple developer teams (working on different projects - and dependencies - but the same platform code base) and I don't want them modifying the grunt tasks directly.

This functionality would be great (from JSHint):
JSHint will start looking for this file in the same directory as the file that's being linted. If not found, it will move one level up the directory tree all the way up to the filesystem root.

This means I would have "component" (each component module has it's own images folder) level options...sweet.

@wearymadness
Copy link
Author

Hi Andi,

do you have a potential timeline for enhancements?

TANX
Andrew

@andismith
Copy link
Owner

Hi,

This is a nice to have enhancement which I just don't have time to write at the moment.

Please feel free to submit a PR if you feel this is important to have.

Thanks,
Andi

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

No branches or pull requests

2 participants