`--protocol` flag breaks `graph init` with `TypeError: Cannot read properties of undefined (reading 'contract')`

[itsjerryokolo]

Which packages are impacted by your issue?

@graphprotocol/graph-cli

Describe the issue

When initialising a new contract using graph init on graph cli: 0.58, adding a --protocol flag breaks the initialisation process.

Reproduction

nil

Steps to Reproduce the Bug or Issue

Run this command graph init --from-contract 0xc9fe4ffc4be41d93a1a7189975cd360504ee361a --protocol ethereum --network mainnet --contract-name Token --index-events

It breaks with the error below when you add the --protocol and --network flags

Expected behavior

Network should be pulled from the network flag instead of displaying undefined network: mainnet

Screenshots or Videos

No response

Platform

@graphprotocol/graph-cli/0.58.0 darwin-arm64 node-v18.16.0

Subgraph Manifest

No response

Subgraph GraphQL Schema

No response

Additional context

No response

[azf20]

@itsjerryokolo do you see the same issue if you don't pass protocol?

[itsjerryokolo]

@azf20 No, just running graph init or graph init --from-contract 0xc9fe4ffc4be41d93a1a7189975cd360504ee361a, and following the prompt, works.

[azf20]

right if you run:

graph init --from-contract 0xc9fe4ffc4be41d93a1a7189975cd360504ee361a  --network mainnet --contract-name Token --index-events

i.e. without the protocol flag (but with the network flag)

[itsjerryokolo]

Yes, just tried this and it worked

graph init --from-contract 0xc9fe4ffc4be41d93a1a7189975cd360504ee361a  --network mainnet --contract-name Token --index-events