Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
WalkthroughDocumentation-only changes: removed the Fuel v2 migration guide, added an experimental Solana HyperIndex doc and sidebar entry, removed the "Mev Commit" row and expanded supported-network listings in HyperRPC/HyperSync docs, and reordered entries in supported-networks.json without functional code changes. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes
Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
supported-networks.json (1)
1-5: Deduplicatecrossfi-mainnetand consider reformatting the arrayThe
supportedNetworksarray currently includessupported-networks/crossfi-mainnettwice in a row:... "supported-networks/crossfi-mainnet","supported-networks/crossfi-mainnet","supported-networks/crossfi-testnet" ...This will likely surface Crossfi mainnet twice wherever this list is rendered. Suggest dropping the extra entry, e.g.:
- ..."supported-networks/crossfi-mainnet","supported-networks/crossfi-mainnet","supported-networks/crossfi-testnet"... + ..."supported-networks/crossfi-mainnet","supported-networks/crossfi-testnet"...Also, the entire array being on a single line makes future diffs and reviews harder; consider pretty‑printing one entry per line in a follow‑up for maintainability.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (6)
docs/HyperIndex/fuel/fuel.md(1 hunks)docs/HyperIndex/solana/solana.md(1 hunks)docs/HyperRPC/hyperrpc-supported-networks.md(1 hunks)docs/HyperSync/hypersync-supported-networks.md(1 hunks)sidebarsHyperIndex.js(1 hunks)supported-networks.json(1 hunks)
🧰 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.mddocs/HyperRPC/hyperrpc-supported-networks.mdsupported-networks.json
🪛 markdownlint-cli2 (0.18.1)
docs/HyperSync/hypersync-supported-networks.md
34-34: Bare URL used
(MD034, no-bare-urls)
34-34: Bare URL used
(MD034, no-bare-urls)
35-35: Bare URL used
(MD034, no-bare-urls)
35-35: Bare URL used
(MD034, no-bare-urls)
🔇 Additional comments (4)
docs/HyperRPC/hyperrpc-supported-networks.md (1)
26-27: Mev Commit removal from HyperRPC networks table looks consistentThe current table no longer lists Mev Commit, and the remaining entries look structurally consistent with the HyperRPC URL pattern and the broader network docs in this PR. No further adjustments needed here.
sidebarsHyperIndex.js (1)
147-159: Confirm Solana doc ID used in sidebarYou’re referencing the new page as
"solana/solana"while the doc frontmatter setsid: solana. Depending on your Docusaurus config, the correct ID might be just"solana"(frontmatter-based) or"solana/solana"(path-based, like"fuel/fuel").Please double‑check that this key matches the actual doc ID so the sidebar link resolves correctly.
docs/HyperSync/hypersync-supported-networks.md (1)
34-122: Expanded HyperSync networks table looks consistentThe enlarged networks table (and Mev Commit removal) looks internally consistent: names, IDs, and
*.hypersync.xyzURLs follow the established pattern, and tiers are populated for each row. Also, Chainweb Testnet 20/21 are not listed here, which aligns with the earlier decision to drop them due to non‑functional endpoints. Based on learnings, this all looks correct.docs/HyperIndex/fuel/fuel.md (1)
13-13: Updated Fuel introduction is clear and accurateThe new intro succinctly states mainnet/testnet support and frames the page as a HyperIndex‑for‑Fuel guide; link and wording look good and consistent with the rest of the doc.
docs/HyperIndex/solana/solana.md
Outdated
| --- | ||
| id: solana | ||
| title: Solana | ||
| sidebar_label: Solana | ||
| slug: /solana | ||
| description: Experimental Solana support in HyperIndex (v3.alpha.3). RPC-only source. Supports Block Handler, Effect API, and Hosted Service. | ||
| --- | ||
|
|
||
| > Experimental. Available since v3-alpha.3. | ||
| > RPC-only source. HyperSync for Solana is not available yet; we’ll consider it if there’s demand. | ||
|
|
||
| ## What’s supported | ||
|
|
||
| - [Block Handler](/docs/HyperIndex/Guides/block-handlers) | ||
| - [Effect API](/docs/HyperIndex/Guides/effect-api) | ||
| - [Hosted Service](/docs/HyperIndex/Guides/hosted-service) | ||
|
|
||
| ## Quickstart | ||
|
|
||
| ```bash | ||
| pnpx envio init solana | ||
| ``` | ||
|
|
||
| ## Notes | ||
|
|
||
| - Uses RPC as the data source (no HyperSync for Solana yet). | ||
| - The Solana Block Handler doesn't automatically fetch the block data, so you have control over the way how you want to fetch the data by using the slot. |
There was a problem hiding this comment.
Fix Hosted Service link, align version string, and tighten wording
A few small cleanup points in this new page:
- Hosted Service link path is likely wrong
Fuel’s doc links Hosted Service as ../Hosted_Service/hosted-service.md, but here it’s:
- [Hosted Service](/docs/HyperIndex/Guides/hosted-service)To avoid a 404 and stay consistent with existing docs, suggest:
- - [Hosted Service](/docs/HyperIndex/Guides/hosted-service)
+ - [Hosted Service](../Hosted_Service/hosted-service.md)- Version string formatting is inconsistent
Frontmatter uses v3.alpha.3 while the body uses v3-alpha.3. Pick one form (whichever matches your actual release tag) and use it in both places, e.g.:
-description: Experimental Solana support in HyperIndex (v3.alpha.3). RPC-only source. Supports Block Handler, Effect API, and Hosted Service.
+description: Experimental Solana support in HyperIndex (v3-alpha.3). RPC-only source. Supports Block Handler, Effect API, and Hosted Service.- Minor wording polish
Last bullet reads a bit awkwardly:
- The Solana Block Handler doesn't automatically fetch the block data, so you have control over the way how you want to fetch the data by using the slot.Consider tightening it to:
- - The Solana Block Handler doesn't automatically fetch the block data, so you have control over the way how you want to fetch the data by using the slot.
+ - The Solana Block Handler doesn't automatically fetch block data, giving you full control over how you fetch it based on the slot.🤖 Prompt for AI Agents
In docs/HyperIndex/solana/solana.md around lines 1 to 27, fix three small
issues: update the Hosted Service link to match existing docs (use the relative
path used elsewhere under Guides/Hosted_Service/hosted-service.md), make the
version string consistent between frontmatter and body by choosing one format
(change either v3.alpha.3 or v3-alpha.3 so both match the project release tag),
and tighten the last bullet’s wording to a clearer sentence (e.g., state that
the Solana Block Handler does not fetch block data automatically and you should
fetch blocks by slot as needed).
|
|
||
|
|
There was a problem hiding this comment.
Hmm, wonder why the script is adding this 🤷 Not an issue at least :)
2 participants
Summary by CodeRabbit
Documentation
New Features
✏️ Tip: You can customize this high-level summary in your review settings.