@ai-matrx/records-ui 0.3.1 → 0.3.2

package/CHANGELOG.md

@@ -1,5 +1,36 @@
 # Changelog — @ai-matrx/records-ui
 
+## 0.3.2
+
+Automatic changed-only republish (docs/metadata drift since the last tag — see
+`git diff npm/records-ui/v0.3.1..npm/records-ui/v0.3.2 -- apps/shared/records-ui`).
+No source changes intended and no consumer action required.
+
+## 0.4.0
+
+**`recordsDataSource` honours the schema the CALLER named, and the two page
+assemblies get their first headless proof.**
+
+0.3.1's adapter routes every `rpc` to one fixed schema (`custom` by default).
+That is right for the store's own doors and wrong for the trust doors:
+`@ai-matrx/records`' `trustDoor` says `iam` out loud — the external principal and
+the publish binding live there — and a fixed-schema adapter sends them to
+`custom`, where PostgREST answers PGRST202 naming a schema the caller never
+asked for. The adapter now reads `options.schema` per call and falls back to the
+second argument (still `custom`) only when a call says nothing, which no caller
+in `@ai-matrx/records` does. The port already specified this: "A host binding
+supabase-js routes this to `client.schema(options.schema).rpc(fn, args)`".
+
+`TablesHome` and `TablePage` shipped in 0.3.1 with no assertion of their own.
+Three now run against the live store in `demo/smoke.test.tsx`: the four lanes
+drawn by name with a real table in one of them and `New table` offered; the
+table page's records plus its five admin rails, with the settings rail really
+opening the panel; and the same page giving a plain member the records and NONE
+of the administering controls — absent, not disabled.
+
+**Consumer action:** none. `recordsDataSource(client)` is unchanged at the call
+site; a host that deliberately wants a different fallback passes it second.
+
 ## 0.3.1
 
 Ships the canonical `TablesHome`, `TablePage`, `RecordsMount`, and table-creation helpers

package/dist/index.cjs

@@ -5677,11 +5677,16 @@ function RecordsMount({
 function personActor(userId) {
   return userId ? { actor: "user", user_id: userId } : { actor: "user" };
 }
-function recordsDataSource(client, schema = "custom") {
+function recordsDataSource(client, fallbackSchema = "custom") {
   const supabase = client;
   return {
-    rpc: (fn, args) => supabase.schema(schema).rpc(fn, args),
-    schema: (name) => supabase.schema(name)
+    rpc(fn, args, options) {
+      const on = supabase.schema(options?.schema ?? fallbackSchema);
+      return on.rpc(fn, args);
+    },
+    schema(name) {
+      return supabase.schema(name);
+    }
   };
 }