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
Currently, when running graph init and trying to scaffold a subgraph indexing a proxy contract, the CLI is not aware of the implementation contract. This is a big caveat for new devs since often, the first contract they want to index is indeed a proxy.
I think this is solvable at the CLI level: Detect if a contract is a proxy contract and if so, present an option to look at the current implementation contract and get the ABI from it to scaffold out the subgraph entities.
Currently, when running
graph init
and trying to scaffold a subgraph indexing a proxy contract, the CLI is not aware of the implementation contract. This is a big caveat for new devs since often, the first contract they want to index is indeed a proxy.I think this is solvable at the CLI level: Detect if a contract is a proxy contract and if so, present an option to look at the current implementation contract and get the ABI from it to scaffold out the subgraph entities.
Read more about the Proxy Upgrade Pattern
The text was updated successfully, but these errors were encountered: