@rebasepro/common 0.15.0 → 0.16.0

package/dist/index.es.js

@@ -2047,7 +2047,7 @@ var buildPropertyCallbacks = (properties) => {
 * rows").
 *
 * **For auth collections additionally**
-*  3. A permissive **self SELECT** grant (`id = auth.uid()`), so users can read
+*  3. A permissive **self SELECT** grant (`id = rebase.uid()`), so users can read
 *     their own row (profile, session bootstrap) without every app re-declaring
 *     it.
 *  4. A **restrictive** admin write gate. Restrictive policies are AND'd with
@@ -2056,7 +2056,7 @@ var buildPropertyCallbacks = (properties) => {
 *     such as "a user may edit their own row". Without this, a permissive owner
 *     rule would let a user change their own `roles`.
 *
-* The server context is recognised as `auth.uid() IS NULL` (`policy.serverContext()`)
+* The server context is recognised as `rebase.uid() IS NULL` (`policy.serverContext()`)
 * — the built-in flows that run without a user (signup, migrations) set no user
 * GUC — which also lets the owner connection satisfy these policies even under
 * FORCE RLS. A *user* request never reaches that state: an anonymous one carries
@@ -2685,8 +2685,8 @@ function buildCollectionFromTableMetadata(tableName, metadata) {
 				operations = ["delete"];
 				break;
 		}
-		const qual = policy.qual ?? void 0;
-		const withCheck = policy.with_check ?? void 0;
+		const qual = policy.qual ? rewriteLegacyRlsFunctions(policy.qual) : void 0;
+		const withCheck = policy.with_check ? rewriteLegacyRlsFunctions(policy.with_check) : void 0;
 		if (qual) securityRules.push({
 			name: policy.policy_name,
 			operations,