This repository has been archived by the owner on Aug 28, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on the suggestion from #5, I thought about implementing a cargo subcommand instead, since it would be closer to what it already provides with
cargo doc
.I kept it pretty simple, it applies these general options to all the files it renders:
Two new arguments to control whether everything goes into singles files or not:
The output file was replaced by the root output directory, under which more directories may be created depending on the previous two arguments. There is also the manifest path argument for cargo.
Three new dependencies were added:
One API change was made to the
extract
method.Clippy suggestions and rustfmt were applied as well, similar to #10.
I'm not really sure what is the correct, standard, best, etc, way to build a cargo subcommand, this was based on a few subcommands I knew and used before.
Signed-off-by: Tiago Nascimento [email protected]