nim-dagger/.gitignore

*
!*/
!*.*

!Makefile

nimcache/

# Executables shall be put in an ignored build/ directory
build/

# Nimble packages
/vendor/.nimble

# vscode
.vscode

# Each developer can create a personal .env file with
# local settings overrides (e.g. WEB3_URL)
.env

.update.timestamp
dagger.nims
deployment-localhost.json
readding gitignore rules 2021-11-24 17:27:09 -06:00			`*`
			`!*/`
			`!.`

			`!Makefile`

adding gitignore 2021-11-23 11:10:14 -06:00			`nimcache/`

			`# Executables shall be put in an ignored build/ directory`
			`build/`

			`# Nimble packages`
			`/vendor/.nimble`

			`# vscode`
			`.vscode`

			`# Each developer can create a personal .env file with`
			`# local settings overrides (e.g. WEB3_URL)`
			`.env`

			`.update.timestamp`
			`dagger.nims`
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			`deployment-localhost.json`