-
Notifications
You must be signed in to change notification settings - Fork 80
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
Need a way to specify toolchain channel for each hook #15
Comments
the hooks using default toolchain enabled on your system, If you want to check your code against different platforms it will be better to do using Github Actions for example https://github.com/logannc/fuzzywuzzy-rs/blob/master/.github/workflows/clippy.yml |
that's a shame this isn't supported. i'm using nightly clippy and nightly rustfmt, and stable otherwise. |
Adding this is really simple, just fork the repo and change the |
i think the issue is wanting to use different toolchains for different checks. |
yes, exactly. |
Formatter should run on nightly Rust, so should clippy the linter. Unfortunately, the pre-commit hook won't let us specify toolchain[1]. Instead, redefine the hook locally, with the right flags. [1]: doublify/pre-commit-rust#15 (comment)
I'm tinkering with a project, right now, which compiles fine with stable rust, but its rustfmt configuration uses a whole bunch of options that are only available with nightly rustfmt. I don't want to switch my default toolchain to nightly just for the sake of this project. It would be nice if it were possible to specify, in
.pre-commit-config.yaml
for this project, that the fmt hook should runcargo +nightly fmt
instead ofcargo fmt
.This doesn't appear to be possible with the args array because that's inserted too late on the command line, e.g.
gives an error message about there not being any file named
+nightly
.The text was updated successfully, but these errors were encountered: