indexing-schema

To define entity types in a GraphQL schema for Envio HyperIndex, declare standard types without the @entity decorator, ensure the first field is id: ID!, and use the entity type directly for relationships. Codegen automatically appends _id to reference fields for TypeScript mappings.

Envio HyperIndex schema relationships support the @derivedFrom directive to model inverse relationships, the @index directive for query optimization, and the @config directive to manage numeric precision during code generation.

GraphQL schema codegen maps scalar types to TypeScript in HyperIndex by converting supported primitives like ID!, String!, Int!, Float!, Boolean!, BigInt!, BigDecimal!, Bytes!, Timestamp!, and Json! into their corresponding TypeScript handler types.

Array rules for GraphQL schema definitions in Envio require proper non-null syntax like [Type!]! for array fields. Following these guidelines ensures correct code generation for TypeScript mappings and proper relationship handling.

Yes, you can use enums in your schema.graphql for Envio data indexing. Enum declarations are fully supported, and their TypeScript type mappings are automatically generated during the codegen process alongside scalar types.

Envio HyperIndex schema codegen fails with relationship errors when entity types omit the mandatory id: ID! first field, incorrectly apply the @entity decorator, or misuse @derivedFrom directives on array fields, violating required codegen constraints.