This repository has been archived by the owner on Jul 1, 2021. It is now read-only.
Move get_chain_config from TrinityConfig to Eth1AppConfig #771
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What was wrong?
The
TrinityConfig
contains aget_chain_config
API that is only meant to be used with the eth1 client. (Notice that theBeaconAppConfig
does already contain a similar API for the specifically for the beacon chain)The name
ChainConfig
should be changed toEth1ChainConfig
to be aligned with theBeaconChainConfig
type and doesn't spark wrong assumptions.How was it fixed?
Moved the
get_chain_config
API from theTrinityConfig
to theEth1AppConfig
Renamed the
ChainConfig
type toEth1ChainConfig
To-Do
Cute Animal Picture