@quadrel-enterprise-ui/framework 20.10.0-beta.139.1 → 20.10.0-beta.140.1

package/fesm2022/quadrel-enterprise-ui-framework.mjs

@@ -27090,13 +27090,25 @@ class QdPageCommitActionExecutor {
                     if (ok)
                         applySuccess();
                 },
-                error: err => console.error('QD-UI | QdPage - Commit action observable errored — form was not marked as saved. Catch errors via catchError() in your handler.', err)
+                error: err => this.handleError(action, err)
             });
         }
         else {
             applySuccess();
         }
     }
+    static handleError(action, err) {
+        if (!action.onError) {
+            console.error('QD-UI | QdPage - Commit action observable errored — form was not marked as saved. Provide an `onError` hook on the action, or handle errors in the handler.', err);
+            return;
+        }
+        try {
+            action.onError(err);
+        }
+        catch (callbackErr) {
+            console.error('QD-UI | QdPage - onError callback threw.', callbackErr);
+        }
+    }
 }
 
 /**
@@ -28874,6 +28886,22 @@ const SAFE_BOTTOM_OFFSET_PX = 64;
  *
  * Please check the relevant interfaces for each page type: `QdPageConfigOverview`, `QdPageConfigCreate`, `QdPageConfigInspect`, and `QdPageConfigCustom`.
  *
+ * #### **Commit Actions**
+ *
+ * Commit actions (`submit`, `save`, `saveDraft`) can either run synchronously (handler returns `void`) or wait on an async result (handler returns `Observable<boolean>`). The framework waits for the first emission, advances the saved-state baseline on `true`, and exposes race-free hooks for side effects so navigation after a successful commit does not trigger the unsaved-changes dialog.
+ *
+ * `onSuccess` runs when the handler emits `true` (after the baseline has advanced), `onError` runs when the handler observable errors — e.g. a failed HTTP request that is not caught inside the pipeline.
+ *
+ * ```ts
+ * submit: {
+ *   handler: (formValues) => this.api.create(formValues).pipe(map(() => true)),
+ *   onSuccess: () => this.router.navigateByUrl('/'),
+ *   onError: (err) => this.notifications.add('', { type: 'critical', i18n: 'i18n.myApp.create.failed' })
+ * }
+ * ```
+ *
+ * The same mechanism applies to `save` and `saveDraft`. For the full contract (success vs. planned `false` vs. error, anti-patterns, `discardUnsavedChanges()`), see `QdPageCommitAction` and its action-specific extensions `QdPageSaveAction`, `QdPageSaveDraftAction`, `QdPageCreateSubmitAction`, and `QdPageInspectSubmitAction`.
+ *
  * #### **Validation/Parameterization**
  *
  * Validation and parameterization are covered in a dedicated chapter in the Storybook. Please check the "Validation" section for more information.
@@ -29328,6 +29356,34 @@ class QdPageComponent {
         this._destroyed$.next();
         this._destroyed$.complete();
     }
+    /**
+     * @description Resets all registered form groups to their last saved snapshot, marking the page
+     * as no longer dirty.
+     *
+     * Intended for explicit consumer-driven discard scenarios where you want subsequent navigation
+     * to bypass the unsaved-changes dialog — for example inside a commit action's `onError` hook
+     * after an auth-expiry response, where the user must be redirected to the login page regardless
+     * of unsaved edits.
+     *
+     * Prefer this over wiring custom bypass logic; it keeps the discard explicit and auditable in
+     * application code.
+     *
+     * @example
+     * ```ts
+     * save: {
+     *   handler: (values) => api.save(values).pipe(map(() => true)),
+     *   onError: (err) => {
+     *     if (err.status === 401) {
+     *       this.pageComponent.discardUnsavedChanges();
+     *       this.router.navigateByUrl('/login');
+     *     }
+     *   }
+     * }
+     * ```
+     */
+    discardUnsavedChanges() {
+        this.formGroupManagerService.restoreFormGroupsFromSnapshot();
+    }
     checkConfigValidity() {
         if (!this.config)
             console.warn('QdUi | QdPageComponent - To configure the page you should provide a valid config.');