refactor(data): route full NextGraph surface through @ng-eventually/client
The app now takes its NextGraph runtime AND types from @ng-eventually/client; the only place that imports the real @ng-org SDK is ngSession (the single injection point for configure()). Lifecycle (init/initNg), data (useShape) and types (ShapeType, DeepSignalSet, NG…) all go through the lib. Test infra (auth-setup, mock harness) and generated ORM bindings keep a direct @ng-org import (documented). Validated: build, @ui 4/4, @data 8/8 against the real broker. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -12,7 +12,7 @@ import { createRoot } from 'react-dom/client';
|
||||
import { NextGraphProvider, useNextGraph } from '../context/NextGraphContext';
|
||||
import { FestipodDataProvider, useFestipodData } from '../context/FestipodDataContext';
|
||||
import { useShape } from '@ng-eventually/client';
|
||||
import type { DeepSignalSet } from '@ng-org/alien-deepsignals';
|
||||
import type { DeepSignalSet } from '@ng-eventually/client';
|
||||
import {
|
||||
FpEventShapeType,
|
||||
FpUserProfileShapeType,
|
||||
|
||||
Reference in New Issue
Block a user