cargo-modules alternatives and similar packages
Based on the "Cargo" category.
Alternatively, view cargo-modules alternatives based on common mentions on social networks and blogs.
-
-
-
-
cargo-deb
DISCONTINUED. A cargo subcommand that generates Debian packages from information in Cargo.toml -
-
cargo-bitbake
cargo extension that can generate BitBake recipes utilizing the classes from meta-rust -
InfluxDB high-performance time series database
Do you think we are missing an alternative of cargo-modules or a related project?
README
cargo-modules
Synopsis
A cargo plugin for showing an overview of a crate's modules.
Motivation
With time, as your Rust projects grow bigger and bigger, it gets more and more important to properly structure your code. Fortunately Rust provides us with a quite sophisticated module system, allowing us to neatly split up our crates into arbitrarily small sub-modules of types and functions. While this helps to avoid monolithic and unstructured chunks of code, it can also make it hard at times to still mentally stay on top of the over-all high-level structure of the project at hand.
This is where cargo-modules comes into play:
Installation
Install cargo-modules via:
cargo install cargo-modules
Usage
Print crate as a tree
cargo modules generate tree <OPTIONS>
USAGE:
cargo-modules generate tree [FLAGS] [OPTIONS]
FLAGS:
--all-features Activate all available features
-h, --help Prints help information
--lib Process only this package's library
--no-default-features Do not activate the `default` feature
-V, --version Prints version information
--verbose Enable verbose messages during command execution
--with-orphans Include orphaned modules (i.e. unused files in /src)
--with-tests Include tests (e.g. `#[cfg(test)] mod tests { … }`)
--with-types Include types (e.g. structs, enums)
OPTIONS:
--bin <bin> Process only the specified binary
--features <features>... List of features to activate. This will be ignored if `--cargo-all-features`
is provided
--focus-on <focus-on> Focus the graph on a particular path's environment
--manifest-path <manifest-path> [default: ./Cargo.toml]
--max-depth <max-depth> The maximum depth of the generated graph relative to the node selected by
'--focus-on'
-p, --package <package> Package to process (see `cargo help pkgid`)
--target <target> rustc target
Print crate as a graph
cargo modules generate graph <OPTIONS>
USAGE:
cargo-modules generate graph [FLAGS] [OPTIONS]
FLAGS:
--all-features Activate all available features
-h, --help Prints help information
--lib Process only this package's library
--no-default-features Do not activate the `default` feature
-V, --version Prints version information
--verbose Enable verbose messages during command execution
--with-externs Include used modules and types from extern crates
--with-orphans Include orphaned modules (i.e. unused files in /src)
--with-tests Include tests (e.g. `#[cfg(test)] mod tests { … }`)
--with-types Include types (e.g. structs, enums)
--with-uses Include used modules and types
OPTIONS:
--bin <bin> Process only the specified binary
--features <features>... List of features to activate. This will be ignored if `--cargo-all-features`
is provided
--focus-on <focus-on> Focus the graph on a particular path's environment
--layout <layout> The graph layout algorithm to use (e.g. dot, neato, twopi, circo, fdp, sfdp)
[default: neato]
--manifest-path <manifest-path> [default: ./Cargo.toml]
--max-depth <max-depth> The maximum depth of the generated graph relative to the node selected by
'--focus-on'
-p, --package <package> Package to process (see `cargo help pkgid`)
--target <target> rustc target
If you have xdot installed on your system, you can run this using:
`cargo modules generate graph | xdot -`
This is the result of using cargo-module to generate a tree or a graph of its own repo using the --lib and --with-types options:
[Tree output of cargo modules generate tree --lib --with-types](docs/tree_output.png)
[Tree output of cargo modules generate graph --lib --with-types | xdot -](docs/graph_output.svg)
No-Color Mode
cargo-modules checks for the presence of a NO_COLOR environment variable that, when present (regardless of its value), prevents the addition of color to the console output.
Contributing
Please read [CONTRIBUTING.md](CONTRIBUTING.md) for details on our code of conduct,
and the process for submitting pull requests to us.
Versioning
We use SemVer for versioning. For the versions available, see the tags on this repository.
License
This project is licensed under the MPL-2.0 – see the [LICENSE.md](LICENSE.md) file for details.
*Note that all licence references and agreements mentioned in the cargo-modules README section above
are relevant to that project's source code only.