Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
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`.
- Loading branch information