embarklabs
/
embark
mirror of https://github.com/embarklabs/embark.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Revert "chore: update hooks examples to destructure dependencies object" 

This reverts commit 448eab724b.
This commit is contained in:
Iuri Matias 2020-01-28 14:53:18 -05:00
parent 75f0639d35
commit 5d4b407bce
1 changed files with 15 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
site/source/docs/contracts_configuration.md
View File

@ -440,8 +440,8 @@ We can specify a condition that decides whether a contract should be deployed by
...
deploy: {
ERC20: {
deployIf: async ({contracts, web3, logger}) => {
return await contracts.Manager.methods.isUpdateApproved().call();
deployIf: async (dependencies) => {
return await dependencies.contracts.Manager.methods.isUpdateApproved().call();
},
deps: ['Manager']
},
@ -450,13 +450,13 @@ deploy: {
...
```
Notice how `contracts` gives access to the `Manager` contract instance. This however, is only possible because `Manager` has been defined as dependency of `ERC20` using the `deps` property. If we're using a Node version that doesn't support async/await, the same can be achieved using promises like this (web3 APIs already return promises):
Notice how `dependencies.contracts` gives access to the `Manager` contract instance. This however, is only possible because `Manager` has been defined as dependency of `ERC20` using the `deps` property. If we're using a Node version that doesn't support async/await, the same can be achieved using promises like this (web3 APIs already return promises):
```
...
ERC20: {
deployIf: ({contracts, web3, logger}) => {
return contracts.Manager.methods.isUpdateApproved().call();
deployIf: (dependencies) => {
return dependencies.contracts.Manager.methods.isUpdateApproved().call();
},
deps: ['Manager']
},
@ -495,8 +495,8 @@ We can specify the `onDeploy` hook to execute code, right after a contract has b
deploy: {
SimpleStorage: {
args: [100],
onDeploy: async ({contracts, web3, logger}) => {
await contracts.SimpleStorage.methods.set(150).send({from: web3.eth.defaultAccount});
onDeploy: async (dependencies) => {
await dependencies.contracts.SimpleStorage.methods.set(150).send({from: dependencies.web3.eth.defaultAccount});
}
}
}
@ -511,8 +511,8 @@ Also, as mentioned above, every deployment hook works with plain promises as wel
...
SimpleStorage: {
args: [100],
onDeploy: ({contracts, web3, logger}) => {
return contracts.SimpleStorage.methods.set(150).send();
onDeploy: (dependencies) => {
return dependencies.contracts.SimpleStorage.methods.set(150).send();
}
}
...
@ -529,8 +529,8 @@ deploy: {
args: [100]
},
},
afterDeploy: ({contracts, web3, logger}) => {
contracts.SimpleStorage.methods.set(150).send({from: web3.eth.defaultAccount});
afterDeploy: (dependencies) => {
dependencies.contracts.SimpleStorage.methods.set(150).send({from: dependencies.web3.eth.defaultAccount});
}
...
```
@ -540,9 +540,9 @@ afterDeploy: ({contracts, web3, logger}) => {
Since we use functions for these deployment hooks, we have to manage errors ourselves. We skipped that step in the above examples to save space, but here is an easy example on how you can do it:
```
onDeploy: async ({contracts, web3, logger}) => {
onDeploy: async (dependencies) => {
try {
await contracts.SimpleStorage.methods.set(85).send({from: web3.eth.defaultAccount});
await dependencies.contracts.SimpleStorage.methods.set(85).send({from: dependencies.web3.eth.defaultAccount});
} catch (e) {
console.error('Error during onDeploy', e);
}
@ -577,8 +577,8 @@ The `logger` is injected as part of the `dependencies` object, so we can use it
```
deploy: {
SimpleStorage: {
onDeploy: async ({contracts, web3, logger}) => {
logger.info('Hello from onDeploy!');
onDeploy: async (dependencies) => {
dependencies.logger.info('Hello from onDeploy!');
}
}
}