Most of the Cargo commands support -p/--package and --manifest-path options which is handy for workspaces.
So the root option in tarpaulin is equivalent to the manifest-path option. I admit name consistency may be better, although I do personally like the --root and -r short form for project root. As for package command I agree that is a good idea and now on the list of things to do. :+1:
EDIT: Jut wondering, is the absence of package a blocker for your project? If so I can move this on my priority list above other enhancements.
I added packages so you can specify one or more package specs i.e. --packages=clap:0.3,cargo:1.0. If you fancy trying it out and seeing if it meets your needs that would be helpful :+1: . I haven't published it yet so you'd have to take the latest version off github for testing it.
Unfortunately when testing to ensure I could close this issue I found my latest release with source analysis broke this functionality. I'm adding the bug label and working on a fix, currently have a partial fix on my pc but working on a fix that doesn't sacrifice new features!
Fixed and tested it on exonum itself with the exonum and sandbox packages :smile:
@xd009642 Thank you, I'm going to try it soon! 馃憤