Omnigraph TS SDK 0.10 - #10
Merged
Merged
Conversation
Pin @modernrelay/omnigraph@0.10.0 in the adapter and the demo app. The consumed SDK surface is signature-stable (export/invokeQuery/ingest/ snapshot/schema and all imported types unchanged; the newly exported ExportRecord matches the NDJSON line shape the loader already parses). SERVER_VERSION moves the drift-warning pin to 0.10.x; the mismatch test now drifts against 0.11.0. Test fixtures re-recorded against a real omnigraph-server 0.10.0. The fixture recorder learned the 0.10 CLI and wire shapes: load --json reports per-table entity counts (summed with a pre-0.10 fallback), and the snapshot response renamed tables (table_key/row_count) to datasets (entity_kind + type_name / entity_count) — manifest keys keep the '<kind>:<Type>' form either way. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Gd3TVitMrMbofTZLmeB37Z
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Moves the adapter and demo to
@modernrelay/omnigraph@0.10.0(from 0.9.0, exact pin both places).Migration assessment (verified via d.ts diff, 0.9 → 0.10)
export,invokeQuery,ingest,snapshot,schema,Omnigraph/OmnigraphOptions/CallOptions/ExportInput/InvokeQueryInput/FetchLike. The only changed method (mutate→ConditionalCallOptions) is not called by orbit.ExportRecordtype matches the NDJSON line shapeclassifyExportLinealready parses — no loader changes needed.SERVER_VERSION0.9.0 → 0.10.0 moves the loader's drift-warning pin; the mismatch test now drifts against 0.11.0.Fixtures
Recorded fixtures regenerated against a real omnigraph-server 0.10.0 (local binaries) via
scripts/omnigraph-fixture.mjs, which learned two 0.10 shapes along the way:load --jsonper-table entity counts, and the snapshottables→datasetsrename (entity_kind/type_name/entity_count); manifest rowCounts keys keep the<kind>:<Type>form.Verification
Full check green: 1,800 tests, including the 134 adapter tests against the re-recorded 0.10 fixtures; both version-drift tests updated and passing.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Gd3TVitMrMbofTZLmeB37Z