@base44-preview/sdk 0.8.56-pr.352.b15ea38 → 0.8.56-pr.353.656b952

package/dist/modules/auth.types.d.ts

@@ -50,7 +50,7 @@ export interface RegisterParams {
     email: string;
     /** User's password. */
     password: string;
-    /** Has no effect. Base44 doesn't verify Turnstile tokens for app users. */
+    /** Optional {@link https://developers.cloudflare.com/turnstile/ | Cloudflare Turnstile CAPTCHA token} for bot protection. */
     turnstile_token?: string | null;
     /** Optional {@link https://docs.base44.com/Getting-Started/Referral-program | referral code} from an existing user. */
     referral_code?: string | null;
@@ -137,11 +137,6 @@ export interface AuthModule {
      * You can update any [custom fields](/developers/backend/resources/entities/user-schema#custom-fields)
      * defined in your User entity schema.
      *
-     * [Field-level security](/developers/backend/resources/entities/security#field-level-security-fls)
-     * `write` rules on custom User fields also apply to this method. If `data` includes a field
-     * the user isn't allowed to write, the call throws a permission error and no fields are
-     * updated.
-     *
      * Updating `role` requires editor access on the app.
      *
      * <Note>
@@ -279,7 +274,7 @@ export interface AuthModule {
      *
      * @param email - User's email address.
      * @param password - User's password.
-     * @param turnstileToken - Has no effect. Base44 doesn't verify Turnstile tokens for app users.
+     * @param turnstileToken - Optional {@link https://developers.cloudflare.com/turnstile/ | Cloudflare Turnstile CAPTCHA token} for bot protection.
      * @returns Promise resolving to login response with access token and user data.
      * @throws Error if the email and password combination is invalid or the user is not registered.
      *

package/dist/modules/connectors.types.d.ts

@@ -81,7 +81,7 @@ export interface ConnectorApiRequest {
 export interface ConnectorApiResponse<T = unknown> {
     /** `true` only when the upstream API returned a 2xx status. Proxy and upstream errors are `false`. */
     success: boolean;
-    /** How far the call progressed. Only `not_sent` proves the provider did not execute it. */
+    /** How far the call progressed. */
     phase: ConnectorApiResponsePhase;
     /** The upstream HTTP status code, or `null` when no response was received. */
     status: number | null;

package/dist/modules/entities.types.d.ts

@@ -684,11 +684,7 @@ export interface EntityHandler<T = any> {
     /**
      * Deletes a single record by ID.
      *
-     * The record moves to the entity's trash. To restore it or delete it permanently,
-     * use **Recently deleted** in the [Data tab](/Building-your-app/Managing-your-app-data)
-     * or the [Restore entity record](/api-reference/restore-entity-record) and
-     * [Permanently delete entity record](/api-reference/permanently-delete-entity-record)
-     * endpoints.
+     * Permanently removes a record from the database.
      *
      * @param id - The unique identifier of the record to delete.
      * @returns Promise resolving to the deletion result.
@@ -704,12 +700,7 @@ export interface EntityHandler<T = any> {
     /**
      * Deletes multiple records matching a query.
      *
-     * The matching records move to the entity's trash. To restore them or delete them
-     * permanently, use **Recently deleted** in the
-     * [Data tab](/Building-your-app/Managing-your-app-data) or the
-     * [Restore entity records](/api-reference/restore-entity-records) and
-     * [Permanently delete entity record](/api-reference/permanently-delete-entity-record)
-     * endpoints.
+     * Permanently removes all records that match the provided query.
      *
      * This isn't a transaction. Each record is deleted on its own, so if the call
      * fails partway, the records already deleted stay deleted. Learn more about
@@ -767,8 +758,6 @@ export interface EntityHandler<T = any> {
      * example, filter by `status: 'pending'` when setting status to `'processed'`.
      *
      * Each matching record is updated on its own, and the call isn't a transaction.
-     * All the update operators in a call, such as `$set`, `$inc`, and `$push`, are
-     * applied to each record in a single write.
      * To claim one record safely, so that only one of 2 users acting at the same
      * time succeeds, pass that record's `id` as a plain value plus the conditions
      * that must still be true, then check `updated` in the response. The conditions
@@ -851,20 +840,6 @@ export interface EntityHandler<T = any> {
      *   // Someone else claimed it first, or it was no longer open
      * }
      * ```
-     *
-     * @example
-     * ```typescript
-     * // Save only if the record hasn't changed
-     * // `version` is a number field defined in the Document schema.
-     * // The edit is saved only if the record is still at the version this user loaded.
-     * const result = await base44.entities.Document.updateMany(
-     *   { id: doc.id, version: doc.version },
-     *   { $set: { body: newBody }, $inc: { version: 1 } }
-     * );
-     * if (result.updated === 0) {
-     *   // Someone else saved a change first. Reload the record and try again.
-     * }
-     * ```
      */
     updateMany(query: Partial<T>, data: Record<string, Record<string, any>>): Promise<UpdateManyResult>;
     /**
@@ -1142,7 +1117,7 @@ type DynamicEntitiesModule = {
  *
  * Every app includes a built-in `User` entity that stores user account information. This entity has special security rules that can't be changed.
  *
- * Regular users can only read and update their own user record. With service role authentication, you can read and update any user, and remove any user except the app owner. A removed user moves to **Recently deleted** for 30 days, where an app editor can restore them, and is then deleted permanently. You can't create users using the entities module. Instead, use the functions of the {@link AuthModule | auth module} to invite or register new users.
+ * Regular users can only read and update their own user record. With service role authentication, you can read, update, and delete any user. You can't create users using the entities module. Instead, use the functions of the {@link AuthModule | auth module} to invite or register new users.
  *
  * ## Generated Types
  *

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@base44-preview/sdk",
-  "version": "0.8.56-pr.352.b15ea38",
+  "version": "0.8.56-pr.353.656b952",
   "description": "JavaScript SDK for Base44 API",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",