nim-codex/tests/contracts/examples.nim

import pkg/ethers
import ../examples

export examples

proc example*(_: type Address): Address =
  Address(array[20, byte].example)
[contracts] Update to new marketplace design 2022-03-17 14:15:04 +01:00			`import pkg/ethers`
[tests] Extract common examples into separate module 2022-03-28 16:44:59 +02:00			`import ../examples`
feat: integrate dagger contracts Integrate dagger contracts from `nim-dagger-contracts` repo. Add `dagger-contracts`, `nim-web3`, and all of `nim-web3`’s transitive deps as submodule deps to `nim-dagger`. Note: `nim-web3` and its transitive deps may no longer be needed when we switch to `nim-ethers`. Add a `testContracts` nimble task to test all of the contracts functionality. Namely, this spins up an ethereum simulator, deploys the contracts (in `dagger-contracts`), runs the contract tests, and finally, regardless of success/error, kills the ethereum sim processes. The nimble task can be run with `./env.sh nimble testContracts`. We also tested `nim-dagger-contracts` as a submodule dep of `nim-dagger`, and while the tests run as expected, the preference is to merge `nim-dagger-contracts` inside of `nim-dagger` for ease of parallel development. There’s also a high probability that `nim-dagger-contracts` is not being used as a dep by other projects. Are there any strong objections to this? Co-authored-by: Michael Bradley <michaelsbradleyjr@gmail.com> 2022-01-25 11:22:58 +11:00
[tests] Extract common examples into separate module 2022-03-28 16:44:59 +02:00			`export examples`
feat: integrate dagger contracts Integrate dagger contracts from `nim-dagger-contracts` repo. Add `dagger-contracts`, `nim-web3`, and all of `nim-web3`’s transitive deps as submodule deps to `nim-dagger`. Note: `nim-web3` and its transitive deps may no longer be needed when we switch to `nim-ethers`. Add a `testContracts` nimble task to test all of the contracts functionality. Namely, this spins up an ethereum simulator, deploys the contracts (in `dagger-contracts`), runs the contract tests, and finally, regardless of success/error, kills the ethereum sim processes. The nimble task can be run with `./env.sh nimble testContracts`. We also tested `nim-dagger-contracts` as a submodule dep of `nim-dagger`, and while the tests run as expected, the preference is to merge `nim-dagger-contracts` inside of `nim-dagger` for ease of parallel development. There’s also a high probability that `nim-dagger-contracts` is not being used as a dep by other projects. Are there any strong objections to this? Co-authored-by: Michael Bradley <michaelsbradleyjr@gmail.com> 2022-01-25 11:22:58 +11:00
[contracts] Update to new marketplace design 2022-03-17 14:15:04 +01:00			`proc example*(_: type Address): Address =`
[tests] Extract common examples into separate module 2022-03-28 16:44:59 +02:00			`Address(array[20, byte].example)`