-
Notifications
You must be signed in to change notification settings - Fork 48
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
Support for cargo workspaces #8
Comments
Very good point. I haven't had a need for workspaces myself yet, thus didn't think of it when building How would you expect the output to look? Something like this?
It might further more make sense to switch from
While Further more I would probably want to keep this feature behind a
Glad you like it! |
I have a project which contains several crates. Rather than providing one single crate modules info, running
But it works fine when using it inside each crate. |
@regexident Sorry, somehow I missed your initial reply. Yes, the output you outlined with the (Rust-specific visibility) syntax looks good to me. |
@U007D no worries. I’m somewhat busy right now but will tackle this as soon as I find some spare time. :) |
…ated) This also gives us some workspace support (you need to choose a target from workspace) Improves #8 but only by not crashing on workspaces. We still show one target. The current assumption of one lib max fails when running in a workspace. Since the current code does not allow to select a specific lib target Also there are more target kinds than bin and lib that might be interesting to parse. We should revist the user experience here or always show the whole workspace.
…ated) This also gives us some workspace support (you need to choose a target from workspace) Improves #8 but only by not crashing on workspaces. We still show one target. The current assumption of one lib max fails when running in a workspace. Since the current code does not allow to select a specific lib target Also there are more target kinds than bin and lib that might be interesting to parse. We should revist the user experience here or always show the whole workspace.
More then 2 years passed, wow!
... which is of no use, because the direct-composition crate is one I'm least interested in. I'll try to work around this, but having proper support would be valuable! To clarify, I don't have a strong idea whether you need to analyze the workspace as a whole (that would step into cargo-deps territory to some extent). Having it on a single crate would be good enough for us today. @regexident how is your situation looking now? Would you be able to |
This should now be fixed with #66 having been merged. 🎉 😃 |
I have a project making use of a cargo workspace, but only the main crate is revealed when I issue a
cargo modules
command.Great tool, thank you!
The text was updated successfully, but these errors were encountered: