Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move addresses and start blocks into networks config #20

Merged
merged 7 commits into from
Jun 6, 2023
Merged

Conversation

EdNoepel
Copy link
Contributor

@EdNoepel EdNoepel commented Jun 5, 2023

Changes

  • Use network lookup table for ERC20 factory contract, as done for the other contracts. Add a fake mainnet address for it to placate unit tests. Rename the table variables more concisely.
  • Update docker-compose to use a known network name which will also appear in the testchain container. Mocked up a POC to prove the containers could communicate with each other and with the host. Replace ETH_RPC_URL environment with ETH_NETWORK, which includes the network name prefix. Updated documentation accordingly.
  • Move address and start block configuration out of subgraph.yml and into networks.json' Note that network now must be specified in the build process. Updated README to explain this.
  • Build against latest version of graph toolset, resolving build error Tim brought to my attention.

@@ -12,8 +12,8 @@
"test": "graph test"
},
"dependencies": {
"@graphprotocol/graph-cli": "0.37.6",
"@graphprotocol/graph-ts": "0.29.1"
"@graphprotocol/graph-cli": ">=0.37.6",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want to automatically update? May be issues with breaking changes

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pinning them had the opposite problem. Tim tried to build, but one of the deps for the older version no longer existed. As a result, he was unable to install the pinned versions.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Imagine that should be resolved by our usage of the lockfile? It was removed entirely from the NPM mirrors?

Copy link
Contributor

@MikeHathaway MikeHathaway left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - just one comment about package.json versioning

Copy link
Contributor

@grandizzy grandizzy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@EdNoepel EdNoepel merged commit 832d7f8 into develop Jun 6, 2023
@EdNoepel EdNoepel deleted the networks branch June 6, 2023 18:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants