* Find minimum start block number * Perform fill if db is empty * Make getStartBlock method public in GraphWatcher * Use dataSources property * Update server template to fill block on start * Avoid passing graphWatcher from generated watcher * Ensure block filling for non-subgraph watchers as well * Remove getStartBlock method from GraphWatcher * Remove graphWatcher property from ServerCmd --------- Co-authored-by: neeraj <neeraj.rtly@gmail.com> |
||
|---|---|---|
| .. | ||
| cache | ||
| cli | ||
| codegen | ||
| graph-node | ||
| ipld-eth-client | ||
| peer | ||
| rpc-eth-client | ||
| solidity-mapper | ||
| test | ||
| tracing-client | ||
| util | ||
| README.md | ||
Watchers Directory
Here contains all the publicly available watchers for your experimenting purposes. For general information on setting up the stack and the CLI commands used to interact with watchers, see the docs directory.
Customizing Watchers
-
Indexing on an event:
-
Edit the custom hook function
handleEvent(triggered on an event) in hooks.ts to perform corresponding indexing using theIndexerobject. -
While using the indexer storage methods for indexing, pass
diffas true if default state is desired to be generated using the state variables being indexed.
-
-
Generating state:
-
Edit the custom hook function
createInitialState(triggered if the watcher passes the start block, checkpoint:true) in hooks.ts to save an initialStateusing theIndexerobject. -
Edit the custom hook function
createStateDiff(triggered on a block) in hooks.ts to save the state in adiffStateusing theIndexerobject. The default state (if exists) is updated. -
Edit the custom hook function
createStateCheckpoint(triggered just before default and CLI checkpoint) in hooks.ts to save the state in acheckpointStateusing theIndexerobject.
-