mirror of https://github.com/Stirling-Tools/Stirling-PDF.git synced 2026-09-02 21:03:34 +03:00

Files

T

EthanHealy01andClaude f7a2c626c9 Persist the workbench session across the editor/processor switch (#7654 )

## What

Switching editor -> processor (or reloading) unmounts every editor
provider, which emptied the workbench. This PR mirrors the workbench
into per-tab sessionStorage and refills an empty one from that record on
the next mount:

- **Files, selection, view and active document survive** the shell
switch and reloads. Each recorded file is resolved to its *current leaf*
version on restore, so a file versioned by a policy or another tab comes
back at its latest state.
- **The switch back lands where the user left**: the processor sidebar's
"editor" button consumes a one-shot return path saved at switch time.
- **The app switch respects unsaved changes**: `useOtherAppSwitch`
(proprietary + saas) now routes through `requestNavigation`, so the same
warning guards it as any other navigation.
- Desktop shadows `WorkbenchSessionPersistence` with a stub (OS-launched
files own boot there).

## How to test

I've run through each of these manually:

- Upload several PDFs in the editor, select a couple, and switch to the
Active Files grid. Click "Open PDF Processor" in the sidebar footer,
then switch back to the editor. The same files, selection and view
should return, and you should land on the editor page you left.
- Open a document in the viewer, then reload the tab. The workbench
should refill and come back on the viewer with the same document active.
- With unsaved changes in a tool, click the processor switch. The
unsaved-changes warning should appear, and the switch should only
proceed if you confirm.
- Open a second browser tab with different files. Each tab should
restore its own workbench independently (the record is per-tab
sessionStorage).
- While in the processor, delete one of the open files from storage,
then switch back. The remaining files should restore and a warning toast
should report "Restored X of Y files".

---------

Co-authored-by: Claude <noreply@anthropic.com>

2026-08-27 10:12:48 +00:00

.claude/agents

playwright (#6025 )

2026-04-27 11:35:50 +01:00

.storybook

deps(frontend): upgrade i18next ecosystem to v26 (#7356 )

2026-08-21 11:32:16 +00:00

editor

Persist the workbench session across the editor/processor switch (#7654 )

2026-08-27 10:12:48 +00:00

scripts

Consolidate buttons and related components (#6787 )

2026-07-07 16:06:56 +00:00

shared/components

Consolidate buttons and related components (#6787 )

2026-07-07 16:06:56 +00:00

.gitignore

a11y: empty the grandfathered Storybook baseline (1,058 → 0) (#7309 )

2026-08-12 09:06:05 +00:00

.oxfmtrc.json

Replace Prettier with Oxfmt (#7422 )

2026-08-24 10:34:12 +00:00

oxlint.config.ts

Fix any type usages in frontend (#7617 )

2026-08-24 10:33:50 +00:00

package-lock.json

Replace Prettier with Oxfmt (#7422 )

2026-08-24 10:34:12 +00:00

package.json

Replace Prettier with Oxfmt (#7422 )

2026-08-24 10:34:12 +00:00

README.md

Replace Prettier with Oxfmt (#7422 )

2026-08-24 10:34:12 +00:00

stylelint.config.mjs

Replace Prettier with Oxfmt (#7422 )

2026-08-24 10:34:12 +00:00

vitest.config.ts

Replace ESLint and dpdm with Oxlint (#7330 )

2026-08-07 16:02:11 +00:00

README.md

Frontend

All frontend commands are run from the repository root using Task:

task frontend:dev — start Vite dev server (localhost:5173)
task frontend:build — production build
task frontend:test — run tests
task frontend:test:watch — run tests in watch mode
task frontend:lint — run linting
task frontend:typecheck — run TypeScript type checking
task frontend:check — run typecheck + lint + test
task frontend:install — install npm dependencies

For desktop app development, see the Tauri section below.

Layout

frontend/ is a workspace containing one or more apps. Today it holds the PDF editor under frontend/editor/; new apps (the developer portal, etc.) will sit alongside it as siblings. Shared tooling — package.json, node_modules, .storybook/, oxlint, oxfmt — lives at frontend/ so every app installs once and lints with the same config.

Environment Variables

The editor's environment variables live in committed .env files at frontend/editor/:

.env — used by all builds (core, proprietary, and as the base for desktop/SaaS)
.env.desktop — additional vars loaded in desktop (Tauri) mode
.env.saas — additional vars loaded in SaaS mode

These files contain non-secret defaults and are checked into Git, so most dev work needs no further setup.

To override values locally (API keys, machine-specific settings), create an uncommitted sibling editor/.env.local / editor/.env.desktop.local / editor/.env.saas.local. Vite automatically layers these on top of the committed files.

Docker Setup

For Docker deployments and configuration, see the Docker README.

Tauri

All desktop tasks are available via Task. From the root of the repo:

Dev

task desktop:dev

This ensures the JLink runtime and backend JAR exist (skipping if already built), then starts Tauri in dev mode.

Build

task desktop:build

This does a full clean rebuild of the backend JAR and JLink runtime, then builds the Tauri app for production.

Platform-specific dev builds are also available:

task desktop:build:dev           # No bundling
task desktop:build:dev:mac       # macOS .app bundle
task desktop:build:dev:windows   # Windows NSIS installer
task desktop:build:dev:linux     # Linux AppImage

JLink Tasks

You can also run JLink steps individually:

task desktop:jlink          # Build JAR + create JLink runtime
task desktop:jlink:jar      # Build backend JAR only
task desktop:jlink:runtime  # Create JLink custom JRE only
task desktop:jlink:clean    # Remove JLink artifacts

Clean

task desktop:clean

Removes all desktop build artifacts including JLink runtime, bundled JARs, Cargo build, and dist/build directories.