skills.rest
namehash
namehashOFFICIAL
Explore all skills by this author →
Website𝕏@NamehashLabsGitHub

migrate-to-omnigraph

Migrate ENS Subgraph queries to Omnigraph with cursor-based pagination.

41|19|Updated Dec 23, 2024
Search Tags:#pagination#migrate#subgraph#ens#omnigraph#query-migration
One-click install
npx skills add https://github.com/namehash/ensnode --skill migrate-to-omnigraph
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrate-to-omnigraph
Source: https://github.com/namehash/ensnode/tree/main/packages/ensskills/skills/migrate-to-omnigraph
Command: npx skills add https://github.com/namehash/ensnode --skill migrate-to-omnigraph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A dedicated migration workflow from the legacy ENS Subgraph API to the ENS Omnigraph is planned, outlining the necessary query rewrites, data-model adaptations, and pagination adjustments, while leaning on dependent skills to guide the implementation.

Core Features & Use Cases

  • Plan and map migration from the Subgraph to Omnigraph, including rewriting queries and aligning data models.
  • Flatten nested connections and convert offset-based pagination to cursor-based pagination to match Omnigraph patterns.
  • Capture and address feature gaps during ENSv2 readiness transitions, with reusable migration primitives from base, ens-protocol, and omnigraph.

Quick Start

Provide your current Subgraph queries and I will translate them into Omnigraph queries with updated pagination and data shaping.

Frequently Asked Questions about migrate-to-omnigraph

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate ENS Subgraph queries to the Omnigraph API?▼

To migrate ENS Subgraph queries to the Omnigraph API, you rewrite queries, flatten nested connections, and convert offset-based pagination to cursor-based pagination for a unified data layer.

What is the best way to convert offset pagination to cursor-based pagination for ENS data?▼

Converting offset pagination to cursor-based pagination for ENS data requires flattening nested connections and adjusting query patterns to match the Omnigraph's unified data model structure.

Why do I need to flatten nested connections when transitioning to the ENS Omnigraph?▼

Flattening nested connections is required when transitioning to the ENS Omnigraph because the unified data layer uses flattened data patterns instead of the legacy Subgraph's deeply nested relational connections.

Does the ENS Omnigraph migration support legacy Subgraph API feature gaps?▼

The ENS Omnigraph migration captures and addresses feature gaps during ENSv2 readiness transitions by utilizing reusable migration primitives from base, ens-protocol, and omnigraph dependencies.

What do I need to provide to start migrating my subgraph queries to Omnigraph?▼

To start migrating your subgraph queries to Omnigraph, you need to provide your current Subgraph queries so they can be translated into Omnigraph queries with updated pagination and data shaping.

Related Skills

Explore More Software Engineering Skills→
namehashnamehash
41

enskit

Query ENS Omnigraph data in React apps with typed, provider-based workflows.

Official
Advanced
namehashnamehash
41

unigraph-sql

Query ENS state via SQL over ENSDb for complex data shapes.

Official
Intermediate
namehashnamehash
41

enssdk

Provide a strongly-typed JavaScript/TypeScript client for the ENS Omnigraph API.

Official
Advanced
rawvegrawveg
40

hashnode-api

Manage Hashnode content and user data via the GraphQL API.

Community
Advanced