@designcrowd/library.brand-page 5.17.25-undo-21 → 5.17.25

package/lib/src/brand-page-maker/stores/brandpage-maker/brandpage-maker-store.d.ts

@@ -177,55 +177,16 @@ export declare const useBrandPageMakerStore: import("pinia").StoreDefinition<"br
     hideChangeTemplateConfirmModal(): void;
     onBackgroundChanged(): void;
     onChangeTemplateConfirmModalCancel(): void;
-    onChangeTemplateConfirmModalConfirm(): Promise<void>;
+    onChangeTemplateConfirmModalConfirm(): void;
     onContentChanged(): void;
     onStyleChanged(): void;
-    onTemplateSelected(payload: OnTemplateSelectedPayload): Promise<void>;
+    onTemplateSelected(payload: OnTemplateSelectedPayload): void;
     setSelectedTabName(payload: any): void;
     showNextNotificationMessage(): Promise<void>;
     updateContent<TContent extends Content, P extends {
         id: string;
         content: TContent;
     }>(payload: P): Promise<void>;
-    /**
-     * Restore every store that the `brandPageData` getter reads from, so undo
-     * and redo bring back the EXACT document state captured at snapshot time.
-     *
-     * `initialiseStoresByBrandPageModelAsync` is too narrow for undo/redo — it
-     * only rehydrates pages, sections, and nav structure, which is enough for
-     * the AI-apply path but leaves navigation styles, backgrounds, button/text/
-     * logo/gallery styles, shop config, and several own-store fields unchanged.
-     * This action mirrors the full hydration surface of `applySelectedTemplate`
-     * (minus the template-specific logo/personalisation logic) so a restore is
-     * a complete round-trip of what `brandPageData` returns.
-     *
-     * Called ONLY by history-store during undo/redo. The history store sets
-     * `isApplyingSnapshot=true` across this call to prevent the deep-watcher
-     * on `brandPageData` from re-capturing the restored state.
-     */
-    /**
-     * Force-commit a `template_switch` entry to the history store, if the
-     * history store has a baseline (which only happens when the undo/redo
-     * feature flag is on — see `BrandPageMaker.mixin.ts`).
-     */
-    _captureTemplateSwitchIfEnabled(): void;
-    applyHistorySnapshot(snapshot: BrandPageModel, activePageId?: string): Promise<void>;
-    _syncLogoSettingsFromSnapshot(snapshot: BrandPageModel): void;
-    /**
-     * Restore the active page after a history apply. The id passed in is
-     * already validated against the restored nav by the history store; if
-     * it's undefined (no entry walking back had a viable page), fall back
-     * to the first/default route so the URL, `routeStore.currentRoute.params`,
-     * `pageNavigation.activePageId`, and the page-tab highlight all line up.
-     *
-     * `setCurrentActivePage` is called explicitly in addition to
-     * `navigateToPageByPageId` because `navigateToPageByPageId` is a no-op
-     * when the router instance is undefined (e.g. SSR / unit tests), but the
-     * Pinia state must still be updated so the sidebar's `currentPage`
-     * getter returns the right page.
-     */
-    _navigateToActivePage(activePageId?: string): void;
-    _fallbackSidebarIfSelectedContentMissing(snapshot: BrandPageModel): void;
     export(): BrandPageModel;
     setBrandPageType({ brandPageType }: {
         brandPageType: BrandPageType;

package/lib/src/brand-page-maker/stores/brandpage-maker/brandpage-maker-store.js

@@ -11,7 +11,7 @@ import { useShopConfigStore } from '@shared/ecommerce-settings/store/shop-settin
 import { usePageNavigationStore } from '@shared/page-navigation/store/page-navigation-store';
 import { applyLogoThemeToBrandPageModel, migrateBrandPageModel, applyUserPersonalisationToBrandPageModelAsync, getBrandPageViewModelFromBrandPageModel, isLogoContent, parseLogoThemeToCssStyles, logoUtil, GetLatestModelVersion, } from '@brand-page/utils';
 import { navigateToPageByPageId } from '../../routing';
-import { BRANDPAGE_DEFAULT_ERROR_MESSAGE_DESCRIPTION, BRANDPAGE_DEFAULT_SAVE_MESSAGE_DESCRIPTION, MAKER_MOBILE_BREAKPOINT, MESSAGE_VISIBLE_DURATION, SIDE_BAR_TAB_NAMES, } from '@brand-page-maker/constants';
+import { BRANDPAGE_DEFAULT_ERROR_MESSAGE_DESCRIPTION, BRANDPAGE_DEFAULT_SAVE_MESSAGE_DESCRIPTION, MAKER_MOBILE_BREAKPOINT, MESSAGE_VISIBLE_DURATION, } from '@brand-page-maker/constants';
 import { useUiSideBarStore } from '@shared/side-bar/store';
 import { delayInMS } from '../../../utils/ui-util';
 import { useUiContentSettingsStore } from '@shared/content-settings/store';
@@ -32,7 +32,6 @@ import { useConsent } from '@brand-page/composables/consent.composable';
 import { commonTr, errorTr } from '@src/composables/useTranslate';
 import { UPGRADE_CTA_LOCATIONS } from '../../composables/useEventTracker';
 import { useVideoStore } from '../video';
-import { useHistoryStore } from '../history/history-store';
 import { findValuesByKey } from '../../../helpers/ts.helper';
 import { useLogoStore } from '../logo-store';
 const brandPageTypeTemplateTypeMap = {
@@ -387,15 +386,6 @@ export const useBrandPageMakerStore = defineStore('brandPageMaker', {
                     description: payload.noDescription ? '' : description,
                 },
             });
-            // Any successful save re-baselines the undo stack so a user can't
-            // undo back past the persisted state. This covers Save Progress /
-            // Publish AND settings-only saves (updateBrandPage,
-            // updateSensitiveContent, admin saveTemplate) — settings-tab
-            // actions persist the metadata, so allowing undo to roll them
-            // back would let the local stack drift from what's saved.
-            // reset() no-ops in non-undo-redo sessions (no baseline = nothing
-            // to clear).
-            useHistoryStore().reset();
         },
         hideChangeTemplateConfirmModal() {
             this.setIsChangeTemplateConfirmModalVisible({
@@ -409,11 +399,10 @@ export const useBrandPageMakerStore = defineStore('brandPageMaker', {
             this.setSelectedTemplateId({ templateId: false });
             this.hideChangeTemplateConfirmModal();
         },
-        async onChangeTemplateConfirmModalConfirm() {
-            await this.applySelectedTemplate();
+        onChangeTemplateConfirmModalConfirm() {
+            this.applySelectedTemplate();
             this.hideChangeTemplateConfirmModal();
             this.isModifiedAfterTemplateApplied = false;
-            this._captureTemplateSwitchIfEnabled();
         },
         onContentChanged() {
             this.setIsModifiedAfterTemplateApplied();
@@ -421,7 +410,7 @@ export const useBrandPageMakerStore = defineStore('brandPageMaker', {
         onStyleChanged() {
             this.setIsModifiedAfterTemplateApplied();
         },
-        async onTemplateSelected(payload) {
+        onTemplateSelected(payload) {
             this.setSelectedTemplateId({
                 templateId: payload.templateId,
             });
@@ -431,8 +420,7 @@ export const useBrandPageMakerStore = defineStore('brandPageMaker', {
                 });
             }
             else {
-                await this.applySelectedTemplate();
-                this._captureTemplateSwitchIfEnabled();
+                this.applySelectedTemplate();
             }
         },
         setSelectedTabName(payload) {
@@ -458,236 +446,6 @@ export const useBrandPageMakerStore = defineStore('brandPageMaker', {
         async updateContent(payload) {
             const uiContentSettingsStore = useUiContentSettingsStore();
             uiContentSettingsStore.updateContent(payload);
-            // NOTE (Bolt 1, 2026-04-23): this action is not the actual edit path used
-            // by the UI — sidebar inputs call uiContentSettingsStore.updateItemValue
-            // directly. History capture is driven by a deep `watch(brandPageData, ...)`
-            // installed in history-store once the baseline is captured, so we do not
-            // need to instrument this action. Kept here as a pass-through because
-            // removing it may affect other callers.
-        },
-        /**
-         * Restore every store that the `brandPageData` getter reads from, so undo
-         * and redo bring back the EXACT document state captured at snapshot time.
-         *
-         * `initialiseStoresByBrandPageModelAsync` is too narrow for undo/redo — it
-         * only rehydrates pages, sections, and nav structure, which is enough for
-         * the AI-apply path but leaves navigation styles, backgrounds, button/text/
-         * logo/gallery styles, shop config, and several own-store fields unchanged.
-         * This action mirrors the full hydration surface of `applySelectedTemplate`
-         * (minus the template-specific logo/personalisation logic) so a restore is
-         * a complete round-trip of what `brandPageData` returns.
-         *
-         * Called ONLY by history-store during undo/redo. The history store sets
-         * `isApplyingSnapshot=true` across this call to prevent the deep-watcher
-         * on `brandPageData` from re-capturing the restored state.
-         */
-        /**
-         * Force-commit a `template_switch` entry to the history store, if the
-         * history store has a baseline (which only happens when the undo/redo
-         * feature flag is on — see `BrandPageMaker.mixin.ts`).
-         */
-        _captureTemplateSwitchIfEnabled() {
-            const historyStore = useHistoryStore();
-            if (!historyStore.baselineCaptured)
-                return;
-            historyStore.captureTemplateSwitch();
-        },
-        async applyHistorySnapshot(snapshot, activePageId) {
-            const styleSettingsStore = useUiStyleSettingsStore();
-            const navigationStyleSettingsStore = useUiNavigationStyleSettingsStore();
-            const backgroundSettingsStore = useUiBackgroundSettingsStore();
-            const pageNavigationStore = usePageNavigationStore();
-            const shopStore = useShopConfigStore();
-            // 1. Pages + header/footer sections (also covers content items).
-            this.initialisePagesForCurrentPage({
-                pages: snapshot.pages,
-                sections: {
-                    [PAGE_SECTIONS.header]: {
-                        [VIEWPORTS.desktop]: snapshot.pageHeaderDesktop,
-                        [VIEWPORTS.mobile]: snapshot.pageHeaderMobile,
-                    },
-                    [PAGE_SECTIONS.footer]: {
-                        [VIEWPORTS.desktop]: snapshot.pageFooterDesktop,
-                        [VIEWPORTS.mobile]: snapshot.pageFooterMobile,
-                    },
-                },
-            });
-            // 2. Page-level nav structure (routes, orders).
-            pageNavigationStore.setNav({ nav: snapshot.nav });
-            // 3. Navigation STYLES (header/footer nav colors, alignment, etc.) —
-            //    this is the bit that was being dropped before.
-            // Use function-form $patch so each nested style object is replaced as a
-            // whole reference. The object-form $patch (used by setState) deep-merges
-            // and would leave keys present in the live state but absent from the
-            // snapshot in place — e.g. switching button styles then undoing would
-            // leave the new style's borderRadius/borderStyle/borderWidth applied.
-            navigationStyleSettingsStore.$patch((state) => {
-                state.navigation[PAGE_SECTIONS.header][VIEWPORTS.desktop] =
-                    new NavigationDesktop(snapshot.pageHeaderDesktop?.navigation);
-                state.navigation[PAGE_SECTIONS.header][VIEWPORTS.mobile] =
-                    new NavigationMobile(snapshot.pageHeaderMobile?.navigation);
-            });
-            // 4. Global styles (logo, button, text, gallery). Same whole-reference
-            //    replacement reasoning as step 3.
-            styleSettingsStore.$patch((state) => {
-                state.buttonStyles = snapshot.styles.buttonStyles;
-                state.logoStyles = snapshot.styles.logoStyles;
-                state.textStyles = snapshot.styles.textStyles;
-                state.galleryStyles = snapshot.styles.galleryStyles;
-            });
-            // 5. Background styles. Same whole-reference replacement reasoning as
-            //    step 3 — `setBackgroundStyles` calls per-field setters that
-            //    `Object.assign` partials onto the live `style` and
-            //    `backgroundShapeStyle` objects, so keys from the previous mode
-            //    (e.g. background image url, shape style props) would survive an
-            //    undo back to a state that doesn't have them.
-            backgroundSettingsStore.$patch((state) => {
-                state.backgroundStyles = snapshot.styles.backgroundStyles;
-            });
-            backgroundSettingsStore.onBackgroundChanged();
-            // 6. Shop products are derived from shop-content blocks inside `pages`,
-            // so they're already implicitly restored at step 1. Re-run the shop
-            // store's derivation to keep `products` in sync with the snapshot
-            // pages. paymentConfig is intentionally NOT restored — selecting it is
-            // backend-confirmed (Stripe Connect / payment-provider linkage) per
-            // project-guardrails.md, so it must persist across undo. We pass the
-            // live paymentConfig back in to preserve it.
-            shopStore.initialiseShopStore({
-                paymentConfig: shopStore.paymentConfig,
-                pages: snapshot.pages ?? [],
-            });
-            // 7. Own-store scalar fields surfaced by the brandPageData getter.
-            if (snapshot.isModifiedAfterTemplateApplied !== undefined) {
-                this.isModifiedAfterTemplateApplied =
-                    snapshot.isModifiedAfterTemplateApplied;
-            }
-            if (snapshot.brandPageType) {
-                this.setBrandPageType({ brandPageType: snapshot.brandPageType });
-            }
-            this.faviconUrl = snapshot.faviconUrl;
-            this.ogImageUrl = snapshot.ogImageUrl;
-            this.measurementID = snapshot.measurementID;
-            this.adsenseID = snapshot.adsenseID;
-            this.ogTitle = snapshot.ogTitle;
-            this.ogDescription = snapshot.ogDescription;
-            this.cookieOptions = snapshot.cookieOptions;
-            this.saveContactSettings = snapshot.saveContactSettings;
-            // 8. Re-sync the logo-settings sidebar's `selectedLogoImage` from the
-            //    restored header logo. The preview rehydrates via the page contents,
-            //    but `uiLogoSettings` holds its own copy that drives the sidebar
-            //    "current logo" state — same pattern as `initialiseStoresByBrandPageModelAsync`.
-            //    Also restores the variations grid + template asset for the
-            //    snapshot's draft token (both are sidecars to `brandPageData` —
-            //    BYO upload mutates them out of band).
-            this._syncLogoSettingsFromSnapshot(snapshot);
-            // 9. If the sidebar is editing a content item that no longer exists in
-            //    the restored page, fall back to the Content tab so the user doesn't
-            //    stare at a blank settings panel.
-            this._fallbackSidebarIfSelectedContentMissing(snapshot);
-            // 10. Switch to the page the user was viewing when this entry was
-            //     captured (or the closest still-existing page if the captured
-            //     page was the one being undone-away). The history store does the
-            //     walk-back resolution and passes us a pageId that's guaranteed to
-            //     exist in the restored nav — or undefined if no entry walking
-            //     back has a viable id, in which case we fall through to the
-            //     first/default route. Without this, the page-tabs carousel keeps
-            //     highlighting whatever page slug is in the URL (which can no
-            //     longer match any nav item after a page-add undo) and the
-            //     sidebar's `currentPage` getter silently falls back to page 0.
-            this._navigateToActivePage(activePageId);
-        },
-        _syncLogoSettingsFromSnapshot(snapshot) {
-            const logoSettingsStore = useUiLogoSettingsStore();
-            const editableLogoStore = useUiEditableLogoStore();
-            const logoStore = useLogoStore();
-            const logoImage = snapshot.brandPageType === BRAND_PAGE_TYPES.default
-                ? snapshot.pages?.[0]?.contents?.find((c) => c.type === 'logo')?.logoImage
-                : snapshot.pageHeaderDesktop?.logoImage;
-            if (!logoImage)
-                return;
-            logoSettingsStore.setState({
-                newState: { selectedLogoImage: logoImage },
-            });
-            const draftToken = logoImage.logoDraftToken;
-            if (!draftToken)
-                return;
-            // Re-derive `enableEditMode` and the active template asset from the
-            // logo-store's draft registry. Drafts are append-only for the session,
-            // and BYO upload stamps `templateAsset` onto the registered draft when
-            // it lands — so the registered draft is enough to fully restore the
-            // sidebar's design/upload chooser without storing anything inside
-            // each history entry. The variations grid is restored from the
-            // editable-logo store's per-token cache (populated by every
-            // `updateEditableLogoImageUrlAsync` render).
-            const draft = logoStore.getLogoDraftAssetByToken(draftToken);
-            if (draft) {
-                editableLogoStore.setEnableEditMode(!draft.isByo);
-                if (draft.templateAsset) {
-                    logoStore.setLogoTemplateAsset(draft.templateAsset);
-                }
-            }
-            editableLogoStore.setLogoDraftToken(draftToken);
-            editableLogoStore.restoreVariationsForDraftToken(draftToken);
-        },
-        /**
-         * Restore the active page after a history apply. The id passed in is
-         * already validated against the restored nav by the history store; if
-         * it's undefined (no entry walking back had a viable page), fall back
-         * to the first/default route so the URL, `routeStore.currentRoute.params`,
-         * `pageNavigation.activePageId`, and the page-tab highlight all line up.
-         *
-         * `setCurrentActivePage` is called explicitly in addition to
-         * `navigateToPageByPageId` because `navigateToPageByPageId` is a no-op
-         * when the router instance is undefined (e.g. SSR / unit tests), but the
-         * Pinia state must still be updated so the sidebar's `currentPage`
-         * getter returns the right page.
-         */
-        _navigateToActivePage(activePageId) {
-            const pageNavigationStore = usePageNavigationStore();
-            let targetPageId = activePageId;
-            if (!targetPageId) {
-                const fallbackRoute = pageNavigationStore.routes.length
-                    ? pageNavigationStore.getFirstOrDefaultRoute()
-                    : undefined;
-                targetPageId = fallbackRoute?.pageId;
-            }
-            if (!targetPageId)
-                return;
-            pageNavigationStore.setCurrentActivePage({ pageId: targetPageId });
-            navigateToPageByPageId(targetPageId);
-        },
-        _fallbackSidebarIfSelectedContentMissing(snapshot) {
-            const contentSettingsStore = useUiContentSettingsStore();
-            const sideBarStore = useUiSideBarStore();
-            const selectedItemId = contentSettingsStore.selectedItemId;
-            if (!selectedItemId)
-                return;
-            const existingContentIds = new Set();
-            snapshot.pages?.forEach((page) => {
-                page.contents?.forEach((content) => {
-                    if (content?.id)
-                        existingContentIds.add(content.id);
-                });
-            });
-            if (existingContentIds.has(selectedItemId))
-                return;
-            // The previously-selected content was undone away. Restore the
-            // Content tab's natural landing state — the same shape produced
-            // when the user clicks the Content tab fresh — instead of leaving
-            // the sidebar stuck rendering `<FocusedContentItemSettings>` for
-            // a missing item, which paints a blank panel.
-            //
-            // `resetMode()` pops the modeStack back to the base `edit` entry
-            // (the default landing mode); clearing `selectedItemId` releases
-            // the pointer to the now-deleted item.
-            sideBarStore.setSelectedTabName({
-                tabName: SIDE_BAR_TAB_NAMES.CONTENT_SETTINGS,
-            });
-            contentSettingsStore.resetMode();
-            contentSettingsStore.selectedItemId = null;
-            contentSettingsStore.selectedItemFieldName = null;
-            contentSettingsStore.selectedItemIndex = null;
-            contentSettingsStore.selectedItemValue = null;
         },
         export() {
             const data = this.brandPageData;

package/lib/src/brand-page-maker/stores/logo-store/logo-store.d.ts

@@ -10,7 +10,6 @@ export interface LogoDraftAsset {
     tick: number;
     isByo: boolean;
     logoEditUrl?: string;
-    templateAsset?: LogoTemplateAsset;
 }
 export interface LogoStoreState {
     logoTemplateAsset?: LogoTemplateAsset;

package/lib/src/brand-page-maker/stores/user/user-store.js

@@ -20,7 +20,6 @@ export const useBrandPageMakerUserStore = defineStore('brandPageMakerUser', {
             canUseAITextGenerator: false,
             canUseGoogleAdsense: false,
             googleAdsenseEnabled: false,
-            canUseUndoRedo: true,
         },
         emailAddress: '',
         hasPremiumSubscription: false,