We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
cargo crev expand <crate> [<version>]
We could cargo-expand for allowing reviewing the crate code conveniently without having to cd to a given directory.
cargo-expand
cd
We should probably expand build.rs and any other file like this too.
build.rs
The text was updated successfully, but these errors were encountered:
cargo crev expand <crate> [<version]
dtolnay/request-for-implementation#6 (comment)
Sorry, something went wrong.
Implemented in https://github.com/TedDriggs/syn-inline-mod.
I have implemented a prototype version of this in d5aec67, but it looks like it will lose all the formatting and comments?
> cargo run --release -- crev crate expand -u foo Finished release [optimized] target(s) in 0.12s Running `target/release/cargo-crev crev crate expand -u foo` # [cfg (test)] mod tests { # [test] fn it_works () { assert_eq ! (2 + 2 , 4) ; } } > cat /home/dpc/.cargo/registry/src/github.com-1ecc6299db9ec823/foo-0.0.0/src/lib.rs #[cfg(test)] mod tests { #[test] fn it_works() { assert_eq!(2 + 2, 4); } }
No branches or pull requests
We could
cargo-expand
for allowing reviewing the crate code conveniently without having tocd
to a given directory.We should probably expand
build.rs
and any other file like this too.The text was updated successfully, but these errors were encountered: