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

Add .fengniaoignore file to auto-exclude files upon running #9

Open
Makazone opened this issue Apr 9, 2017 · 1 comment
Open

Add .fengniaoignore file to auto-exclude files upon running #9

Makazone opened this issue Apr 9, 2017 · 1 comment

Comments

@Makazone
Copy link

Makazone commented Apr 9, 2017

Currently, you have to supply exclude paths via inline arguments fengniao --exclude Pods. However, in situations when your app displays assets based on image names returned by API you will want to exclude a lot of files/paths.

It will be handy to have an .ignore like file similar to .gitignore so that each time I run fengniao I won't need to remember which files I need to exclude.

This file could be called .fengniaoignore and be structured similarly to .gitignore.

Let me know what you think about it and I can make a PR for it.

Thanks for the handy utility!

@onevcat
Copy link
Owner

onevcat commented Apr 9, 2017

@Makazone

Hey, thanks for the suggestion.

Currently you could just write a simple shell script for it. However, I agree with you that there could be a better way.

Instead of a .ignore file, I believe it would be better if we could have something like a "config" file, and then pass it as a config option to the command line. Maybe something like this when using:

fengniao --configuration fengniao.json

By doing so, beside of the exclude paths, we could also pass other parameters from the file and make things easier.

Sure, a p-r is warmly welcome for it, even you'd only implement the "exclude" part (and I could do other parts of it later). If you think it's better to have a standalone ignore file, please also let me know and we could have more discuss on it! :)

Thank you.

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

2 participants