@protobase/config 0.67.5 → 0.67.7

package/dist/config.d.ts

@@ -98,7 +98,8 @@ export type ProtobaseConfig = AppKeys & ApiOptionKeys & {
   mobile?: MobileConfig;
   /**
    * `true` keeps the tables the app's users add in its own database and serves each one like a resource of the config;
-   * `protobase migration` writes the schemas they need. Off by default, and refused together with organizations.
+   * `protobase migration` writes the schemas they need. Off by default. With organizations, each keeps its own tables;
+   * refused with `authenticate.organizations` alone.
    */
   userTables?: boolean;
 };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@protobase/config",
-  "version": "0.67.5",
+  "version": "0.67.7",
   "description": "defineConfig and the types of a Protobase project's protobase.config.ts, and the JSON Schema of protobase.config.json.",
   "license": "Apache-2.0",
   "repository": {
@@ -31,6 +31,6 @@
     "access": "public"
   },
   "peerDependencies": {
-    "@protobase/server": "0.67.5"
+    "@protobase/server": "0.67.7"
   }
 }

package/schema.json

@@ -1013,7 +1013,7 @@
       ]
     },
     "userTables": {
-      "description": "`true` keeps the tables the app's users add in its own database and serves each one like a resource of the config;\n`protobase migration` writes the schemas they need. Off by default, and refused together with organizations.",
+      "description": "`true` keeps the tables the app's users add in its own database and serves each one like a resource of the config;\n`protobase migration` writes the schemas they need. Off by default. With organizations, each keeps its own tables;\nrefused with `authenticate.organizations` alone.",
       "anyOf": [
         {
           "type": "boolean"