Currently contracts.json is hard coded in several places of the client. Would be better to be using a component implemented in a separate module so changes can be made in one place.
This contracts.json file is created by the deploy.js script, so we need to change this script to be more configurable.
The next step is to easily allow for the contract configuration to use a different exported JSON file based on which network is being used. Example development, rinkeby, main, etc. This way we can persist and reuse these configurations once deployed.
On #33
Currently
contracts.jsonis hard coded in several places of the client. Would be better to be using a component implemented in a separate module so changes can be made in one place.This
contracts.jsonfile is created by thedeploy.jsscript, so we need to change this script to be more configurable.The next step is to easily allow for the contract configuration to use a different exported JSON file based on which network is being used. Example
development,rinkeby,main, etc. This way we can persist and reuse these configurations once deployed.