Lesson 7: why use helper-hardhat-config?

[hamednasr]

Why do we construct a new file "helper-hardhat-config.js" ?? why not use this

const networkConfig = {
4: {
name: "rinkeby",
ethUsdPriceFeed: "0x8A753747A1Fa494EC906cE90E9f37563A8AF630e"
},

in the file "hardhat-config.js" ???

[krakxn]

It would lead to a circular dependency, and also as it is irrelevant in hardhat-config.js

We intend on keeping the contents inside hardhat-config.js solely for importing packages which Hardhat requires, and further configurations for Hardhat. So, it's relevance is solely for Hardhat and should be kept that way. Or, put simply, contents only which Hardhat needs.

Hardhat does not need to know of our networkConfig, we are using it for our own logic.

Put simply, networkConfig does not belong there and only used for OUR purposes, so we make a helper config.

You definitely could do that, but it would go against following the Modularity principle of Software Engineering - of keeping modules' content relevant to itself. It is also easier to debug this way, when everything has its own attribute. Put simply, keeping things specific to themselves.

Hope this helps!

[hamednasr]

thank you so much!!