docs: more improvements in docs examples#2148
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThis PR updates omnigraph documentation and examples, refactors a URL builder function with proper capitalization, tightens component type contracts, enriches GraphQL response fixtures, and removes an unused package export. ChangesOmnigraph documentation and API refinements
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Suggested labels
🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (3 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 |
Greptile SummaryThis PR makes several small improvements to the ENSNode docs: fixes a function name casing (
Confidence Score: 5/5Safe to merge — all changes are documentation and example data with no runtime logic affected. All changes are confined to docs content, example mock data, a function rename with a single updated call site, a prop type narrowing, and removal of an unused package export path. No application logic, API, or data pipeline is altered. responses.json — the domain-resolver mock response still lacks the Important Files Changed
Reviews (2): Last reviewed commit: "Merge branch 'main' into ll/docs-example..." | Re-trigger Greptile |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?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: 3
🤖 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/integration-options/enskit/example.mdx`:
- Around line 20-22: Update the "StackBlitz embed outage" caution block so the
outage date includes the year: replace the phrase "as of **May 19**" with "as of
**May 19, 2026**" (or the correct year) in the caution block text to make the
date explicit and unambiguous.
In
`@docs/ensnode.io/src/content/docs/docs/integrate/integration-options/enssdk/example.mdx`:
- Around line 20-22: Update the caution block titled "StackBlitz embed outage"
so the outage date is unambiguous by replacing the bare "May 19" text with a
full date including year (for example "May 19, 2026"); locate the string
"StackBlitz is having problems with embedded WebContainer projects as of **May
19**" in the file and change it to include the year (e.g., "**May 19, 2026**")
while preserving the surrounding Markdown/caution formatting.
In `@packages/ensnode-sdk/package.json`:
- Around line 20-22: The package.json export removed the subpath
"./omnigraph-api/example-queries", which is a breaking change for consumers;
restore a compatibility export entry for "./omnigraph-api/example-queries" that
points to the previous module (or add a small re-export file like
src/omnigraph-api/example-queries.ts that re-exports the original symbols and
reference it in "exports"), or alternatively document and perform this change
only behind a major-version bump and deprecation notice; update the "exports"
map to include "./omnigraph-api/example-queries": "<path-to-reexport>" so
imports targeting that subpath continue to resolve.
🪄 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: 4f5dabb3-4ce4-453c-9cab-654f3e7787bd
📒 Files selected for processing (9)
docs/ensnode.io/src/components/molecules/OmnigraphAPIExamplePanels.astrodocs/ensnode.io/src/components/organisms/OmnigraphAPIExample.astrodocs/ensnode.io/src/content/docs/docs/integrate/integration-options/enskit/example.mdxdocs/ensnode.io/src/content/docs/docs/integrate/integration-options/enssdk/example.mdxdocs/ensnode.io/src/content/docs/docs/integrate/omnigraph/schema-reference.mdxdocs/ensnode.io/src/content/docs/docs/services/ensrainbow/concepts/creating-files.mdxdocs/ensnode.io/src/data/omnigraph-examples/responses.jsondocs/ensnode.io/src/lib/playground/utils.tspackages/ensnode-sdk/package.json
lightwalker-eth
left a comment
lightwalker-eth
left a comment
There was a problem hiding this comment.
@sevenzing Looks good, thanks for the updates 👍
2 participants
Lite PR
Tip: Review docs on the ENSNode PR process
Summary
Small fixes in docs
Why
Testing
Notes for Reviewer (Optional)
Pre-Review Checklist (Blocking)