-
-
Notifications
You must be signed in to change notification settings - Fork 407
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
Make "structopt" dependency optional #239
Comments
@adumbidiot that sounds fine to me, is this something you wanted to look at? |
Yeah sure |
Another option would be to separate the crate into two: |
@Razican sounds interesting, would it still be easy to develop against the CLI when working against the lib? Ive not split 2 crates in the same project before |
@jasonwilliams it should be easy, yes. Both crates would be in the same repo, with a I can do a PR this week to see how it would look like, but I think it should be fairly easy. |
The
structopt
dependency seems to be only used for the binaries. It would be nice if it could be disabled if this engine was used as a library. Maybe it could be put behind acli
feature flag or similar and enabled for the binaries only?The text was updated successfully, but these errors were encountered: