@rebasepro/common 0.0.1-canary.2 → 0.0.1-canary.4d4fb3e

package/README.md

@@ -138,7 +138,7 @@ You can replace the Firebase Storage implementation with your own.
 ## Included example
 
 You can access the code for the demo project under
-[`example`](https://github.com/Rebaseco/rebase/tree/master/example). It includes
+[`example`](https://github.com/rebasepro/rebase/tree/master/example). It includes
 every feature provided by this CMS.
 
 Keep in mind you need to update the dependencies in that project if you want to

package/dist/collections/CollectionRegistry.d.ts

@@ -1,9 +1,9 @@
 import { EntityCollection } from "@rebasepro/types";
 export declare class CollectionRegistry {
-    private collectionsByDbPath;
+    private collectionsByTableName;
     private collectionsBySlug;
     private rootCollections;
-    private rawCollectionsByDbPath;
+    private rawCollectionsByTableName;
     private rawCollectionsBySlug;
     private rawRootCollections;
     private lastRawInputSnapshot;

package/dist/data/buildRebaseData.d.ts

@@ -0,0 +1,14 @@
+import { DataDriver, RebaseData } from "@rebasepro/types";
+/**
+ * Build a `RebaseData` object from a `DataDriver` using JavaScript Proxy.
+ *
+ * This is the key bridge: any property access like `data.products` returns
+ * a `CollectionAccessor` backed by the underlying DataDriver, without
+ * needing per-collection code generation.
+ *
+ * @example
+ * const data = buildRebaseData(driver);
+ * await data.products.create({ name: "Camera", price: 299 });
+ * const { data: items } = await data.products.find({ where: { status: "eq.published" } });
+ */
+export declare function buildRebaseData(driver: DataDriver): RebaseData;

package/dist/index.d.ts

@@ -1,2 +1,3 @@
 export * from "./util";
 export * from "./collections";
+export * from "./data/buildRebaseData";