-
Notifications
You must be signed in to change notification settings - Fork 317
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
refactor(nervous-system): Remove ic-sns-governance and ic-sns-init's …
…test_feature configurations (#1606) [← Previous PR](#1609) There are two reasons to have a --test_feature target: 1. The crate itself has different functionality when cfg(feature = "test") is true 2. The crate is a library that depends on crate that has a --test_feature target, and needs to give the choice to its consumer whether the dependency has --test_feature enabled. The second rule is "viral" which has lead to a massive outbreak of crates with a `--test_feature` target. In fact most of our crates that had a --test_feature target were in the second category. The root cause of most of these was that SNS Governance's library had a `--test_feature` target. This PR: 1. Moves the logic for determining whether we are in "test mode" to the canister crate (from the library crate) 2. Remove's SNS Governance's library's --test-feature target 3. Remove's SNS Init's --test-feature target, which did nothing after #1609 4. Reverses the viral outbreak of --test-feature now that these two crates no longer needed it. The following crates have had their --test-feature removed entirely: 1. `//rs/sns/init:init--test_feature` 2. `//rs/sns/governance:governance--test_feature` 4. `//rs/nns/governance/api:api--test_feature` 5. `//rs/nns/sns-wasm:sns-wasm--test_feature` 6. `//rs/sns/cli:cli--test_feature` 7. `//rs/sns/swap:swap--test_feature` 8. `//rs/nns/governance/init:init--test_feature` 8. `//rs/nns/gtc:gtc--test_feature` And some others no longer depend on any --test_feature crates, which is useful for development
- Loading branch information
Showing
19 changed files
with
104 additions
and
294 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.