Move the package to the @ng-eventually scope
This repository is a sibling of @ng-org/refine-providers, not a successor: that one binds a Refine application to the NextGraph SDK as it is today, this one will bind it to @ng-eventually/polyfill, which stands in for the SDK that has not shipped yet. Both have a legitimate existence and an application may move from one to the other. The scope says which of the two a dependency line is asking for.
This commit is contained in:
@@ -44,7 +44,7 @@ If you created a `note.shex` file, this will generate three files in the `/orm`
|
||||
Now within the `shapes` directory, create a `shapeTypes.ts` like this:
|
||||
|
||||
```ts
|
||||
import { ShapeTypes } from "@ng-org/refine-providers";
|
||||
import { ShapeTypes } from "@ng-eventually/refine-providers";
|
||||
import { NoteShapeType } from "./orm/note.shapeTypes";
|
||||
|
||||
const shapeTypes : ShapeTypes = {
|
||||
@@ -61,7 +61,7 @@ if several users are working on the same data. See the example app for how to ha
|
||||
in the edit and view pages.
|
||||
|
||||
```tsx
|
||||
import { authProvider, dataProvider, liveProvider } from "@ng-org/refine-providers";
|
||||
import { authProvider, dataProvider, liveProvider } from "@ng-eventually/refine-providers";
|
||||
import shapeTypes from "./shapes/shapeTypes";
|
||||
|
||||
const ngAuthProvider = authProvider();
|
||||
|
||||
Reference in New Issue
Block a user