feat(docs): add visuals and explanations for ENS name healing process#2270
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughUpdated ChangesENS Label Healing Documentation
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
There was a problem hiding this comment.
Pull request overview
Updates the ENS Subgraph “Key limitations” documentation to better explain the ENS name healing problem (unhealed labelhashes) and visually illustrate the impact and current/target healing coverage, positioning ENSNode’s Omnigraph + ENSRainbow as the solution.
Changes:
- Adds a plain-language explanation of encoded labelhashes with real-world examples.
- Adds new visuals (unhealed profile example, healing coverage chart, healed vs unhealed split).
- Updates the healing-coverage comparison copy to reference ENSRainbow and current coverage numbers.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
`@docs/ensnode.io/src/content/docs/docs/integrate/ens-subgraph/key-limitations.mdx`:
- Around line 184-186: Update the MDX copy that currently states "ENSRainbow has
healed 259,053,605 unknown labels so far" to include a timestamp (e.g., "as of
26 May 2026") immediately after the numeric count so the snapshot is
date-stamped; edit the tip block containing the "Omnigraph API" / ENSRainbow
paragraph to append "as of <DATE>" (or use the same date used in the image alt
text) and ensure the wording matches the alt text for consistency.
- Line 180: The text uses three ASCII dots in the label example "[428...b0b]";
replace that sequence with the single typographic ellipsis character so it reads
"[428…b0b]" (use U+2026) to match the other occurrence and keep typography
consistent across the document.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 09693754-f606-4942-894e-6a11f46cb5c2
⛔ Files ignored due to path filters (3)
docs/ensnode.io/src/assets/ens-profile-unhealed.svgis excluded by!**/*.svgdocs/ensnode.io/src/assets/healed-name-split.pngis excluded by!**/*.pngdocs/ensnode.io/src/assets/healing-coverage.pngis excluded by!**/*.png
📒 Files selected for processing (1)
docs/ensnode.io/src/content/docs/docs/integrate/ens-subgraph/key-limitations.mdx
Greptile SummaryThis PR enriches the "Unhealed names" section of the ENS Subgraph key-limitations doc with three new visual assets (an SVG illustration and two PNGs) and supporting prose that explains what labelhash names look like, how healing coverage compares across implementations, and how ENSRainbow resolves the problem.
Confidence Score: 4/5Safe to merge after fixing the broken The only functional defect is the missing docs/ensnode.io/src/content/docs/docs/integrate/ens-subgraph/key-limitations.mdx — broken link on line 185. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[Reader lands on key-limitations page] --> B[Sees 'Unhealed names' section]
B --> C[New: Intro paragraph + Example links]
C --> D[New: ens-profile-unhealed.svg]
D --> E[Updated tip callout — ENSRainbow stats]
E --> F[New: healing-coverage.png chart]
F --> G[New: Explanatory prose about healed names]
G --> H[New: healed-name-split.png comparison]
H --> I[Link to ENSRainbow service docs]
Reviews (2): Last reviewed commit: "Update docs/ensnode.io/src/content/docs/..." | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
lightwalker-eth
left a comment
lightwalker-eth
left a comment
There was a problem hiding this comment.
@djstrong looks good, thanks 👍
…ey-limitations.mdx
|
|
||
| :::tip[~94% healed, and climbing] | ||
| The [Omnigraph API](/docs/integrate/omnigraph) already heals **~94%** of these labels, compared to roughly **10%** with the label set bundled in the traditional ENS Subgraph — and climbing toward a **99%** target. | ||
| ENSNode already heals **~94%** of these labels with [ENSRainbow](/docs/services/ensrainbow), compared to **~11%** with the label set bundled into the traditional ENS Subgraph. [ENSRainbow](ensrainbow.io) has data for healing **259,053,605** unknown labels as of May 2026, and coverage is climbing toward a **99%** target. |
Lite PR
Tip: Review docs on the ENSNode PR process
Summary
Why
Testing
Notes for Reviewer (Optional)
Pre-Review Checklist (Blocking)