History

Jonathan Rainville 87a04cd5db fix(@embark/contracts-manager): always deploy contracts with deploy: true This was an issue experienced with ENS contracts not being deployed because the configs used `strategy: explicit` and ENS configs are not in configs. To fix, I changed the way we check for deploy. If `deploy` is set as `true` it should always deploy even if not in configs. It just means they were added from a plugin (like ENS) Also, I needed to set to `false` the `deploy` property of contracts compiled that were not in config, because otherwise, they tried to deploy, which goes against the strategy. This is because those contracts get initiated as `deploy: true`.		2020-02-07 14:23:45 -05:00
..
src	fix(@embark/contracts-manager): always deploy contracts with deploy: true	2020-02-07 14:23:45 -05:00
.npmrc	move embarkjs packages & remove embark- prefix from some folders (#1879 )	2019-09-06 18:26:08 -04:00
CHANGELOG.md	chore(prerelease): 5.2.0-nightly.0	2020-02-07 00:12:17 +00:00
README.md	chore: update site urls	2020-01-28 12:07:17 -05:00
package.json	chore(prerelease): 5.2.0-nightly.0	2020-02-07 00:12:17 +00:00
tsconfig.json	build: implement collective typecheck	2019-12-13 13:59:47 -05:00
tslint.json	move embarkjs packages & remove embark- prefix from some folders (#1879 )	2019-09-06 18:26:08 -04:00

`embark-contracts-manager`

Smart contracts manager for Embark