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
Is there any reason why event signatures cannot contain named parameters in a subgraph manifest?
Surely the graph-cli could strip out the names from the signatures when looking for the corresponding match in the ABI.
Other indexers like Envio require the event signatures to contain the names of the parameters, which makes code reusability between our subgraphs difficult.
Logs
I am getting this error when trying to run codegen with a subgraph manifest that contains named parameters:
✖ Failed to load subgraph from manifests/ethereum.yaml: Error in manifests/ethereum.yaml:
Path: dataSources > 0 > eventHandlers > 0
Event with signature 'Approval(indexed address from,indexed address to,uint256 value)' not present in ABI 'SablierFlow'.
Available events:
- Approval(indexed address,indexed address,indexed uint256)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Idea
Is there any reason why event signatures cannot contain named parameters in a subgraph manifest?
Surely the
graph-cli
could strip out the names from the signatures when looking for the corresponding match in the ABI.Other indexers like Envio require the event signatures to contain the names of the parameters, which makes code reusability between our subgraphs difficult.
Logs
I am getting this error when trying to run
codegen
with a subgraph manifest that contains named parameters:Beta Was this translation helpful? Give feedback.
All reactions