You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I try to initialize a subgraph, I'm forced to select a public chain from the registry. It's a pretty common use-case to start developing a subgraph against a local hardhat/anvil node.
$ graph init
› Warning: In next major version, this flag will be removed. By default we will
› stop initializing a Git repository.
? Network … localhost
Other · other network not on the list
< 112 more - type to filter >
Selecting other exits the wizard:
graph init
› Warning: In next major version, this flag will be removed. By default we will
› stop initializing a Git repository.
✔ Network · N/A
The chain list is populated from the Networks Registry:
https://github.com/graphprotocol/networks-registry
To add a chain to the registry you can create an issue or submit a PR
The text was updated successfully, but these errors were encountered:
Good point.
I like having "Other" option that gives you a way out if you can't find the chain you are looking for. From UX perspective.
Perhaps we can add "Local Node" as an option here.
When I try to initialize a subgraph, I'm forced to select a public chain from the registry. It's a pretty common use-case to start developing a subgraph against a local hardhat/anvil node.
Selecting
other
exits the wizard:The text was updated successfully, but these errors were encountered: