-
Notifications
You must be signed in to change notification settings - Fork 11
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
convert into cli #2
Comments
Do you prefer (1) one binary per folder or (2) a single cli that allows access to all tools? Personally, I think a single cli with all commands works best, we can have something like:
If this is what you want, I can work on it using a library that I recently wrote just for this kind of scenario. |
Also, as an unrelated note, I can convert this project to go modules if you want. |
Hey! Yea, second option sounds better. I didn't want to go for it because it felt a bit too complex but if we can make it happen then that would be awesome. Also, yes go modules will be cool too. I don't know why but I keep running into weird errors like "this file is not a part of X package" while it actually is when I try using go modules. |
That was fast! Alright, will look into it and update you :) |
@gaurav-gogia , check PR #15 to see if it is acceptable or if you have any other suggestions. |
Sure, will look into it now :) |
Each folder has its own main package file. I was wondering if a simple CLI added for each so that they could be run more easily. More details can be discussed in this thread.
I get that my above description is a bit vague but its just that I couldn't find better words. I'll try my best to answer your queries though
The text was updated successfully, but these errors were encountered: