indexing-handler-syntax

Register Polymarket indexer event handlers using Contract.Event.handler to expose event, context, and chain information. This standardizes handler registration and provides a consistent API for accessing event data within HyperIndex.

The context API in HyperIndex allows you to read and write entities, perform getWhere queries, and access runtime information like chainId, isLive, and context.log. It provides a consistent interface for interacting with indexer runtime data during event processing.

Safely update entities in an indexer event handler by using spread updates to ensure immutability while applying changes. This pattern prevents unsafe mutations and maintains data integrity throughout the HyperIndex runtime execution.

Undefined fields in indexer handlers often occur from misusing _id suffixes or unsafe mutations. Avoid these common pitfalls by applying spread updates correctly and following safe patterns for entity CRUD operations within the context API.

Yes, you can leverage the indexer runtime API to introspect contracts, chains, and handlers during development. This allows you to validate runtime execution in a test environment and inspect available runtime information.

Common pitfalls when writing event handlers include encountering undefined fields, misusing _id suffixes, and performing unsafe mutations. Enforcing safe patterns and correct spreading of entities guards against these errors in HyperIndex handler development.