hotfix: correctly embed new embedded data entities#2163
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
3 Skipped Deployments
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughInterpreted scalar parsing logic is simplified by removing helper function calls and using direct type casts, while graphcache is configured to treat three additional entity types as non-keyable embedded data to suppress cache warnings. ChangesOmnigraph Schema and Cache Updates
🎯 2 (Simple) | ⏱️ ~8 minutes
🚥 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 docstrings
🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
ESLint skipped: no ESLint configuration detected in root package.json. To enable, add 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 hotfix addresses two gaps introduced when new schema entity types were added: missing cache-exchange registrations in enskit and a broken import in the ensapi scalar parser.
Confidence Score: 5/5Both changes are targeted and correct — safe to merge. The cache-exchange addition covers exactly the three new entity types that lack an id field in the schema, and a schema audit confirms no other non-keyable types are missing. The scalar change removes a redundant validation call that was already performed by the zod .check() guard immediately before it, and the functions being removed were never part of the public enssdk API. No files require special attention. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[GraphQL Response] --> B{urql graphcache}
B --> C{Has id field?}
C -- Yes --> D[Normalize by id]
C -- No --> E{In keys map?}
E -- EMBEDDED_DATA --> F[Store inline, no normalization]
E -- Not registered --> G[⚠️ Warning: cannot normalize]
subgraph Previously Missing
H[CanonicalName]
I[DomainCanonical]
J[DomainResolver]
end
subgraph Already Registered
K[Label]
L[WrappedBaseRegistrarRegistration]
M[AccountId - custom key fn]
end
H & I & J --> F
K & L --> F
Reviews (1): Last reviewed commit: "hotfix: correctly embed new embedded dat..." | Re-trigger Greptile |
see title