Allow network localhost durning graph init

[schmidsi]

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

[schmidsi]

It should continue the flow but forcing to specify a path to an ABI file instead of trying to download the ABI from a blockexplorer in my opinion.

[YaroShkvorets]

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.

[YaroShkvorets]

Just checked earlier versions of graph cli and not seeing "localhost" option. How was it handled before?

[schmidsi]

It wasn't. It's a new feature request.

[YaroShkvorets]

Based on further discussions with @p-diogo the flow should go like this:

1. User selects "Other" or "Custom" network
2. Enters custom network ID with default being "localhost"
3. Gets a warning with a suggestion to add this network to the registry
4. Manually specifies ABI path, start block and contract name