Do not use `Option` to wrap `GenesisConfig` fields (#8275)
Currently we wrap every `GenesisConfig` field in an `Option`, while we require `Default` being implemented for all pallet genesisconfigs. Passing `None` also results in the genesis not being initialized, which is a bug as seen from the perspective of a pallet developer? This pr changes the fields of the `GenesisConfig` to non `Option` types.
Showing
- substrate/bin/node-template/node/src/chain_spec.rs 10 additions, 10 deletionssubstrate/bin/node-template/node/src/chain_spec.rs
- substrate/bin/node/cli/src/chain_spec.rs 34 additions, 34 deletionssubstrate/bin/node/cli/src/chain_spec.rs
- substrate/bin/node/testing/src/genesis.rs 28 additions, 28 deletionssubstrate/bin/node/testing/src/genesis.rs
- substrate/frame/collective/src/lib.rs 5 additions, 5 deletionssubstrate/frame/collective/src/lib.rs
- substrate/frame/elections-phragmen/src/lib.rs 4 additions, 4 deletionssubstrate/frame/elections-phragmen/src/lib.rs
- substrate/frame/elections/src/mock.rs 4 additions, 4 deletionssubstrate/frame/elections/src/mock.rs
- substrate/frame/example/src/lib.rs 4 additions, 4 deletionssubstrate/frame/example/src/lib.rs
- substrate/frame/support/src/genesis_config.rs 10 additions, 12 deletionssubstrate/frame/support/src/genesis_config.rs
- substrate/frame/support/test/tests/instance.rs 10 additions, 10 deletionssubstrate/frame/support/test/tests/instance.rs
- substrate/frame/support/test/tests/issue2219.rs 2 additions, 2 deletionssubstrate/frame/support/test/tests/issue2219.rs
Please register or sign in to comment