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

Proposal: Searching for config file from . to / #61

Open
croogie opened this issue Dec 8, 2017 · 1 comment
Open

Proposal: Searching for config file from . to / #61

croogie opened this issue Dec 8, 2017 · 1 comment

Comments

@croogie
Copy link

croogie commented Dec 8, 2017

It would be great to don't call the script in the directory where .ccarc is but rather call it from some child directory eg. src/main/components.
What create-component-app can do then is that he will look for .ccarc file starting from current directory to every parent directory (so ..,../.. etc) till he find config file (similarly how node look for node_modules dir).

When config file will be found then you can assume that path param is not needed. Script should create files where it has been executed.

This may be quite a change but I think it will be more usable then passing everytime --path parameter (which btw is not that bad - but for sure can be better).

What do you think about that?

@CVarisco
Copy link
Owner

Hi @croogie !

sorry for the delay in the answer, I'm a little bit busy in this period 🙁
Anyway, I like your idea but I need to think a little bit about how we can implement this without break all the cases that the tool managed.
In the next days I'll work on other things and when I have time to think about it I'll do.

If you want, you can try to contribute, I appreciate a lot of contributions to the project 🏆

@CVarisco CVarisco changed the title Searching for config file from . to / Proposal: Searching for config file from . to / Jan 22, 2018
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