watcher-ts/packages/codegen

Code Generator

Setup

• In root of the repository:

  • Install required packages:

    yarn
    

  • Build files:

    yarn build
    

Run

Follow the steps below or follow the demos:

• Subgraph watcher

• Non subgraph watcher

Steps:

• Create a .yaml config file in the following format for generating a watcher:

  # Example config.yaml
  # Contracts to watch (required).
  # Can pass empty array ([]) when using subgraphPath.
  contracts:
      # Contract name.
    - name: Example
      # Contract file path or an url.
      path: ../graph-node/test/contracts/Example.sol
      # Contract kind (should match name of dataSource in {subgraphPath}/subgraph.yaml if subgraphPath provided)
      kind: Example1
  
  # Output folder path (logs output using `stdout` if not provided).
  outputFolder: ../test-watcher
  
  # Code generation mode [eth_call | storage | all | none] (default: none).
  mode: none
  
  # Kind of watcher [lazy | active] (default: active).
  kind: active
  
  # Watcher server port (default: 3008).
  port: 3008
  
  # Solc version to use (optional)
  # Use longVersion prefixed with v from the release list https://binaries.soliditylang.org/bin/list.json
  # If not defined, uses solc version listed in dependencies
  solc: v0.8.0+commit.c7dfd78e
  
  # Flatten the input contract file(s) [true | false] (default: true).
  flatten: true
  
  # Config for subgraph (optional)
  # Can set empty contracts array if this config is set
  subgraph:
    # Path to subgraph repo directory containing package.json
    directory: ../graph-node/test/subgraph/example1
  
    # Package manager that is used in subgraph repo for dependencies
    packageManager: yarn
  
    # Path to subgraph manifest/config file
    configFile: ../graph-node/test/subgraph/example1/subgraph.yaml
  
    # Networks config file path used when building subgraph (optional)
    # networkFilePath:
  
    # Network configuration to use from the networks config file (optional)
    # network:
  
    # Path to the subgraph build (optional)
    # Subgraph build WASM files should be compiled using @cerc-io/graph-cli
    # If this is set codegen does not use the build generated from subgraph.directory and subgraph.configFile
    # buildPath: ../graph-node/test/subgraph/example1/build
  
  # NOTE: When passed an *URL* as contract path, it is assumed that it points to an already flattened contract file.
  

• Ensure dependencies are installed in the contracts repository before generating the watcher

• Run the following command to generate a watcher from contract(s):

  yarn codegen --config-file <config-file-path>
  

  • config-file(alias: c): Watcher generation config file path (yaml) (required).

  • continue-on-error (alias: e): To continue generation if any unhandled data type is encountered (optional).

  Example:

  • Generate code using a config file config.yaml:

    yarn codegen --config-file ./config.yaml
    

  • Generate code ignoring any unhandled data types:

    yarn codegen --config-file ./config.yaml --continue-on-error
    

  This will create a folder containing the generated code at the path provided in config. Follow the steps in Run Generated Watcher to setup and run the generated watcher.

Development

• lint

  Command to check lint issues in files

  yarn lint
  

  To fix lint issue

  yarn lint --fix
  

• version:set

  Command to set cerc-io package versions in package.json template

  yarn version:set <VERSION>
  

  Example

  yarn version:set 0.2.17
  

Run Generated Watcher

Setup

• Run the following command to install required packages:

  yarn
  

• In the config file (environments/local.toml):

  • Update the state checkpoint settings.

• Create the databases configured in environments/local.toml.

Customize

• Indexing on an event:

  • Edit the custom hook function handleEvent (triggered on an event) in src/hooks.ts to perform corresponding indexing using the Indexer object.

  • While using the indexer storage methods for indexing, pass diff as 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 src/hooks.ts to save an initial State using the Indexer object.

  • Edit the custom hook function createStateDiff (triggered on a block) in src/hooks.ts to save the state in a diff State using the Indexer object. The default state (if exists) is updated.

  • Edit the custom hook function createStateCheckpoint (triggered just before default and CLI checkpoint) in src/hooks.ts to save the state in a checkpoint State using the Indexer object.

Run

• Run lint:

  yarn lint
  

• Run the watcher:

  yarn server
  

• If the watcher is an active watcher:

  • Run the job-runner:

    yarn job-runner
    

  • To watch a contract:

    yarn watch:contract --address <contract-address> --kind <contract-kind> --checkpoint <true | false> --starting-block [block-number]
    

  • To fill a block range:

    yarn fill --start-block <from-block> --end-block <to-block>
    

  • To create a checkpoint for a contract:

    yarn checkpoint --address <contract-address> --block-hash [block-hash]
    

  • To reset the watcher to a previous block number:

    • Reset state:

      yarn reset state --block-number <previous-block-number>
      

    • Reset job-queue:

      yarn reset job-queue
      

  • To export the watcher state:

    yarn export-state --export-file [export-file-path]
    

  • To import the watcher state:

    yarn import-state --import-file <import-file-path>
    

  • To inspect a CID:

    yarn inspect-cid --cid <cid>
    

Known Issues

• Currently, node-fetch v2.6.2 is being used to fetch from URLs as v3.0.0 is an ESM-only module and ts-node transpiles to import it using require.