-
Notifications
You must be signed in to change notification settings - Fork 121
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
fotmat.stable should invoke cargo fmt using default rustfmt #160
Comments
true. in the past, they kept changing their cli and were not backward compatible (as you can see). |
That was fast! :-) Yes, invoking rustfmt in CI builds and in general used to be a huge PITA due to the breaking API changes. Happily, these days are finally behind us. I'm going over my old crates and updating them to the new toolchain - e.g., adding |
clippy already exists. [tasks.clippy]
description = "Runs clippy code linter."
category = "Test"
install_crate = { crate_name = "clippy", rustup_component_name = "clippy-preview", binary = "cargo-clippy", test_arg = "--help" }
command = "cargo"
args = ["clippy"] |
Ugh, I missed that. Thanks! |
pushed to branch 0.16.0 so you can install from that dev branch and test it. |
release as part of 0.16.0 |
Shouldn't
tasks.format-stable
be modified to invoke a simplecargo fmt
, using the defaultrustfmt
, now that it is stable at version 1.0.0 as part of the rust 2018 / 1.31.0 release? The current recipe fails since the-write-mode
parameter is no longer recognized.The text was updated successfully, but these errors were encountered: