rationale: if someone just copies and pastes the recipes over, the --workspace and --all-targets should do no harm but also will not cause surprises when user adds an subcrate. The user might not want to have all of their test code ran through clippy, so they might choose to just use --examples --bins --benches for example. building and testing the workspace doesn't seem to cause issues in crates without a workspace.
this brings the configuration to more in line with cargo fmt --all ..., which does work on all of the workspace.
I haven't used the auditor one so can't comment if it should have some --workspace switch as well though it's configuration doesn't seem to hint at it.
rationale: if someone just copies and pastes the recipes over, the --workspace and --all-targets should do no harm but also will not cause surprises when user adds an subcrate. The user might not want to have all of their test code ran through clippy, so they might choose to just use --examples --bins --benches for example. building and testing the workspace doesn't seem to cause issues in crates without a workspace.
this brings the configuration to more in line with
cargo fmt --all ...
, which does work on all of the workspace.I haven't used the auditor one so can't comment if it should have some --workspace switch as well though it's configuration doesn't seem to hint at it.