Skip to content

Conversation

@keenbeen32
Copy link
Collaborator

@keenbeen32 keenbeen32 commented Dec 30, 2025

Added a page in the migrating to envio section on converting queries from thegraph to envio syntax. Includes info on the query converter tool.

Summary by CodeRabbit

Documentation

  • Added Query Conversion Guide with syntax mapping, conversion rules, and hosted converter tool for migrating from TheGraph to Envio
  • Introduced documentation for Hoodi and Injective network integrations
  • Updated supported networks lists for HyperRPC and HyperSync services

✏️ Tip: You can customize this high-level summary in your review settings.

@vercel
Copy link

vercel bot commented Dec 30, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
envio-docs Ready Ready Preview, Comment Dec 30, 2025 1:24pm

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Dec 30, 2025

📝 Walkthrough

Walkthrough

This PR adds documentation for two new supported networks (Hoodi and Injective) across HyperIndex, HyperRPC, and HyperSync platforms. It introduces a new Query Conversion Guide to clarify GraphQL syntax differences between TheGraph and Envio, updates the migration guide with references to this guide, and updates sidebar navigation and the supported networks manifest.

Changes

Cohort / File(s) Summary
Network Documentation Pages
docs/HyperIndex/supported-networks/hoodi.md, docs/HyperIndex/supported-networks/injective.md
New documentation pages describing Hoodi (TESTNET tier) and Injective (BRONZE tier) integration with Envio, including network overview, tier information, and YAML configuration examples for network setup.
Migration & Query Guidance
docs/HyperIndex/migration-guide.md, docs/HyperIndex/Guides/query-conversion.md
Updated migration guide to reference a new dedicated Query Conversion Guide that explains GraphQL syntax differences between TheGraph and Envio, includes conversion rules (entity names, pagination, filters, types), a hosted converter tool, and example transformations.
Supported Networks Tables
docs/HyperRPC/hyperrpc-supported-networks.md, docs/HyperSync/hypersync-supported-networks.md
Added Hoodi (ID 560048) and Injective (ID 1776) to the supported networks tables in both HyperRPC and HyperSync documentation with corresponding endpoints and tier designations.
Configuration & Navigation
sidebarsHyperIndex.js, supported-networks.json
Added new sidebar entry for Guides/query-conversion and expanded supported-networks manifest with entries for supported-networks/hoodi and supported-networks/injective.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

Suggested reviewers

  • nikbhintade
  • moose-code
  • DenhamPreen

Poem

🐰 Hoppy networks, Hoodi and Injective bound,
Query conversion rules all around!
New guides and docs in sidebar they rest,
GraphQL clarity — documentation's best!

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'Kv/query converter' is vague and references an internal branch name rather than describing the actual changes. It does not clearly communicate that the PR adds query conversion documentation and support for Hoodi/Injective networks. Consider using a more descriptive title like 'Add query conversion guide and support for Hoodi/Injective networks' to clearly convey the main changes to reviewers scanning the history.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
  • 📝 Generate docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
docs/HyperIndex/Guides/query-conversion.md (1)

11-11: Consider tightening the phrasing on introduction.

The phrase "important differences to be aware of when migrating" is slightly verbose. Consider alternatives like "important differences to note when migrating" or "important differences you should know about" for more concise writing.

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 51a2547 and f6318b4.

📒 Files selected for processing (5)
  • docs/HyperIndex/Guides/query-conversion.md
  • docs/HyperIndex/migration-guide.md
  • docs/HyperRPC/hyperrpc-supported-networks.md
  • docs/HyperSync/hypersync-supported-networks.md
  • sidebarsHyperIndex.js
🚧 Files skipped from review as they are similar to previous changes (3)
  • docs/HyperIndex/migration-guide.md
  • sidebarsHyperIndex.js
  • docs/HyperRPC/hyperrpc-supported-networks.md
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-07-29T14:30:03.677Z
Learnt from: DenhamPreen
Repo: enviodev/docs PR: 673
File: docs/HyperIndex/supported-networks/chainweb-testnet-21.md:14-16
Timestamp: 2025-07-29T14:30:03.677Z
Learning: Chainweb Testnet 20 (ID: 5920) and Chainweb Testnet 21 (ID: 5921) have non-functional HyperSync endpoints that return HTTP 404, indicating these networks are not properly supported and should be removed from documentation.

Applied to files:

  • docs/HyperSync/hypersync-supported-networks.md
🪛 LanguageTool
docs/HyperIndex/Guides/query-conversion.md

[style] ~11-~11: To make your writing concise, consider an alternative.
Context: ...there are some important differences to be aware of when migrating. This guide covers all ...

(AWARE_OF)


[grammar] ~26-~26: Ensure spelling is correct
Context: ...exer. This allows you to continue using TheGraph query syntax without making any changes...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[style] ~311-~311: Using many exclamation marks might seem excessive (in this case: 10 exclamation marks for a text that’s 5081 characters long)
Context: ..., BigDecimal|String, numeric|$id: ID!$id: String!` | --- ## Getting Help If you encoun...

(EN_EXCESSIVE_EXCLAMATION)

🪛 markdownlint-cli2 (0.18.1)
docs/HyperSync/hypersync-supported-networks.md

95-95: Bare URL used

(MD034, no-bare-urls)


95-95: Bare URL used

(MD034, no-bare-urls)


96-96: Bare URL used

(MD034, no-bare-urls)


96-96: Bare URL used

(MD034, no-bare-urls)


97-97: Bare URL used

(MD034, no-bare-urls)


97-97: Bare URL used

(MD034, no-bare-urls)

🔇 Additional comments (10)
docs/HyperIndex/Guides/query-conversion.md (9)

15-32: Converter tool section is well-structured and informative.

The section effectively introduces the converter tool, provides repository access, explains the hosted endpoint option for dedicated tier users, and includes appropriate beta warnings with issue reporting links. Clear and actionable guidance for users.


36-79: Entity name conversion rules are clear with practical examples.

The examples effectively demonstrate the conversion from TheGraph's pluralized camelCase (pools, factories, tokens) to Envio's singular PascalCase (Pool, Factory, Token), including both the _by_pk syntax and where clause alternatives. This gives users flexibility in how they structure their queries.


81-117: Pagination parameter conversions are accurate and well-documented.

The firstlimit and skipoffset conversions are correctly described with clear examples. The distinction between the two approaches is helpful for migration.


119-139: Ordering syntax consolidation is correctly explained.

The consolidation of separate orderBy and orderDirection parameters into a single order_by: {field: direction} object is accurately documented with examples for both ascending and descending order.


141-189: Filter operators section provides comprehensive conversion mappings.

The equality, comparison, and negation operators are thoroughly covered with correct mappings:

  • field: valuefield: {_eq: value}
  • _not, _not_in_neq, _nin
  • Comparison operators (_gt, _gte, _lt, _lte, _in) correctly preserved

The examples are practical and demonstrate the nesting structure clearly.


191-223: String filter conversions are accurate with proper wildcard usage.

The mapping of TheGraph's string operators to Envio's _ilike with wildcard patterns is correctly documented:

  • _contains_ilike: "%text%"
  • _starts_with_ilike: "text%"
  • _ends_with_ilike: "%text"
  • Negations using _not wrapper are correctly shown

The examples cover both case-sensitive and case-insensitive variations. Well structured.


225-297: Variable type conversions are comprehensive and accurate.

The mappings correctly specify the type system changes:

  • IDString
  • BytesString
  • BigIntnumeric
  • BigDecimalnumeric

Each conversion includes practical query examples showing the parameter usage in context. The distinction between required (!) and optional types is preserved in the examples.


301-311: Summary table provides excellent quick reference.

The summary table effectively condenses all conversion rules into an easy-to-scan format with category, TheGraph syntax, Envio syntax, and examples. Users can quickly locate relevant conversions without reading the full sections.


315-320: Getting Help section provides clear support pathways.

Directs users to file GitHub issues for converter-specific problems and Discord for general questions. Appropriate triage and clear call-to-action links.

docs/HyperSync/hypersync-supported-networks.md (1)

95-95: The bare URL linting concern applies to the entire table, not just these new entries.

Lines 95 (Hoodi) and 97 (Injective) follow the identical URL pattern used consistently across all 87+ network entries in the table. If MD034 violations are a concern, they should be addressed project-wide, not singled out for new additions. Review the existing entries (Chiliz, Citrea Testnet, etc.) which use the same bare URL style, or confirm whether this pattern is intentionally accepted for markdown table formatting in your documentation standards.

Likely an incorrect or invalid review comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants