mirror of https://github.com/embarklabs/embark.git
349b2691c3
## Issue 1 - “register” section missing When the “register” section of `namesystem.json` was missing, ENS would not deploy the ENS contracts nor create the contracts’ artifacts. ### Fix 1 Fix ENS deployment routine to always deploy the ENS contracts. In the case of testnet/mainnet, the contracts’ addresses will be known and therefore will be understood as “already deployed” by the contract deployer. ## Issue 2 - “register” section exists for non-dev environment Additionally, if a root domain was specified in the “register” section and the DApp connected to an external node where we do not own the ENS contracts (ie testnet), attempting to register a root domain would not be possible as we do not own the ENS contracts. ### Fix 2 Fix ENS deployment routine to check if we are on a network in which we own the ENS contracts. If we are not, and we have specified a “register” section, print a warning to the user that the registration will be ignored. Additionally, remove the “register” section. |
||
|---|---|---|
| .. | ||
| api.js | ||
| ensContractAddresses.js | ||
| ensContractConfigs.js | ||
| index.js | ||