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 it is possible to mention a non-existent function as the handler for an event in the manifest. graph build will run fine, but running the actual subgraph will break at runtime, the first time the event fires that needs to call that handler.
The build step should check if the ts file or wasm have the function defined.
Reproduction
NA
Steps to Reproduce the Bug or Issue
Create a manifest that handles an event but does not have the handler defined.
Deploy it and have the subgraph break with an error
Expected behavior
The build command should catch cases where the hander is missing.
Screenshots or Videos
No response
Platform
OS: Linux
NodeJS: 18.17.1
"@graphprotocol/graph-cli": "^0.59.0"
Subgraph Manifest
No response
Subgraph GraphQL Schema
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Which packages are impacted by your issue?
@graphprotocol/graph-cli
Describe the issue
Currently it is possible to mention a non-existent function as the
handler
for anevent
in the manifest.graph build
will run fine, but running the actual subgraph will break at runtime, the first time the event fires that needs to call thathandler
.The
build
step should check if thets
file orwasm
have the function defined.Reproduction
NA
Steps to Reproduce the Bug or Issue
handler
defined.Expected behavior
The
build
command should catch cases where thehander
is missing.Screenshots or Videos
No response
Platform
Subgraph Manifest
No response
Subgraph GraphQL Schema
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: