diff options
| author | bors <bors@rust-lang.org> | 2022-07-29 00:54:10 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2022-07-29 00:54:10 +0000 |
| commit | 53a09d48557119d2b2a875d77a284b470a95e1c8 (patch) | |
| tree | fd82d31620516b010f550a537ff3084469e48f80 /tests/codegen/src-hash-algorithm/src-hash-algorithm-sha256.rs | |
| parent | 3c7e7dbc1583a0b06df5bd7623dd354a4debd23d (diff) | |
| parent | ea25ef10cf942172e09b463c305b934fabccc8e2 (diff) | |
| download | rust-53a09d48557119d2b2a875d77a284b470a95e1c8.tar.gz rust-53a09d48557119d2b2a875d77a284b470a95e1c8.zip | |
Auto merge of #9252 - Metaswitch:use-deprecated-config, r=Jarcho
Read and use deprecated configuration (as well as emitting a warning) Original change written by `@flip1995` I've simply rebased to master and fixed up the formatting/tests. This change teaches the configuration parser which config key replaced a deprecated key and attempts to populate the latter from the former. If both keys are provided this fails with a duplicate key error (rather than attempting to guess which the user intended). Currently this on affects `cyclomatic-complexity-threshold` -> `cognitive-complexity-threshold` but will also be used in #8974 to handle `blacklisted-names` -> `disallowed-names`. ``` changelog: deprecated configuration keys are still applied as if they were provided as their non-deprecated name. ``` - [x] `cargo test` passes locally - [x] Run `cargo dev fmt`
Diffstat (limited to 'tests/codegen/src-hash-algorithm/src-hash-algorithm-sha256.rs')
0 files changed, 0 insertions, 0 deletions