4 Commits

Include renames

Author	SHA1	Message	Date
3 people	0a50e765b7	Restructure/frontend editor (#6404) ... ## Move editor under `frontend/editor/` Pure restructure: `frontend/` becomes the workspace, `frontend/editor/` holds the PDF editor. 1775 file renames + 40 wiring edits. No logic changes. ### Why `frontend/` is currently the editor — its `src/`, `public/`, `src-tauri/`, config files all sit at the root. Promoting `frontend/` to a workspace and putting the editor in a sibling folder leaves room for future apps to drop in alongside it, sharing one `package.json` / `node_modules` / lint config / Storybook. ### What moves frontend/ ├── editor/ ← NEW: everything editor-specific │ ├── src/ ← was frontend/src/ │ ├── public/ ← was frontend/public/ │ ├── src-tauri/ ← was frontend/src-tauri/ │ ├── index.html, vite.config.ts, vitest.config.ts, playwright.config.ts │ ├── tsconfig*.json, tailwind.config.js, postcss.config.js │ ├── scripts/ │ ├── .env, .env.desktop, .env.saas │ └── DeveloperGuide.md ├── package.json, package-lock.json, node_modules/ ← workspace install ├── eslint.config.mjs, .prettierrc, .prettierignore ← shared tooling ├── .gitignore └── README.md ### Wiring edits (40 files) - `.taskfiles/frontend.yml`, `desktop.yml`, `e2e.yml` - `build.gradle`, `app/core/build.gradle` - `eslint.config.mjs`, `frontend/package.json`, `.gitignore`, `.prettierignore` - `docker/frontend/Dockerfile` - 8 `.github/workflows/*.yml`, plus `.github/dependabot.yml`, `.github/config/.files.yaml`, `.github/labeler-config-srvaroa.yml` - `scripts/translations/**` - Docs: `AGENTS.md`, `CLAUDE.md`, `ADDING_TOOLS.md`, `DeveloperGuide.md`, `WINDOWS_SIGNING.md`, `devGuide/HowToAddNewLanguage.md`, `frontend/README.md`, `frontend/editor/DeveloperGuide.md` Plus 3 renamed + edited: `editor/vite.config.ts` (env path + node_modules walk-up), `editor/scripts/setup-env.mts` (renamed from `.ts` for `import.meta.url`), `editor/scripts/build-provisioner.mjs` (resolve src-tauri relative to script). ### Verification | Check | Result | |---|---| | `task frontend:typecheck:all` (6 variants) | exit 0 | | `task frontend:lint` (eslint + dpdm) | exit 0 | | `task frontend:format:check` | exit 0 | | `task frontend:test` | 657 tests pass, 50 files | | `task frontend:build:{core,proprietary,saas,desktop,prototypes}` | all green | | `task desktop:build` | full Tauri pipeline → `Stirling-PDF_2.11.0_x64_en-US.msi` | | `playwright test --list --project=stubbed` | 172 tests discovered | `task desktop:build` exercises the heaviest path — Rust + WiX + MSI bundle against the moved `editor/src-tauri/`. If anything in the restructure was wrong it wouldn't have built. ### Test plan - [ ] `frontend-validation.yml` green - [ ] `e2e-stubbed.yml` green - [ ] `tauri-build.yml` green on at least one platform - [ ] `check_toml.yml` runs on a translation-touching PR --------- Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>	2026-05-22 13:40:34 +01:00
Anthony StirlingandGitHub	65a3eeca76	Toml (#5115) ... # Description of Changes <!-- Please provide a summary of the changes, including: - What was changed - Why the change was made - Any challenges encountered Closes #(issue_number) --> --- ## Checklist ### General - [ ] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [ ] I have read the [Stirling-PDF Developer Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/DeveloperGuide.md) (if applicable) - [ ] I have read the [How to add new languages to Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md) (if applicable) - [ ] I have performed a self-review of my own code - [ ] My changes generate no new warnings ### Documentation - [ ] I have updated relevant docs on [Stirling-PDF's doc repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/) (if functionality has heavily changed) - [ ] I have read the section [Add New Translation Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags) (for new translation tags only) ### Translations (if applicable) - [ ] I ran [`scripts/counter_translation.py`](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/docs/counter_translation.md) ### UI Changes (if applicable) - [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR) ### Testing (if applicable) - [ ] I have tested my changes locally. Refer to the [Testing Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/DeveloperGuide.md#6-testing) for more details.	2025-12-03 09:57:00 +00:00
LudyandGitHub	299d52c517	refactor: move modules under app/ directory and update file paths (#3938) ... # Description of Changes - **What was changed:** - Renamed top-level directories: `stirling-pdf` → `app/core`, `common` → `app/common`, `proprietary` → `app/proprietary`. - Updated all path references in `.gitattributes`, GitHub workflows (`.github/workflows/*`), scripts (`.github/scripts/*`), `.gitignore`, Dockerfiles, license files, and template settings to reflect the new structure. - Added a new CI job `check-generateOpenApiDocs` to generate and upload OpenAPI documentation. - Removed redundant `@Autowired` annotations from `TempFileShutdownHook` and `UnlockPDFFormsController`. - Minor formatting and comment adjustments in YAML templates and resource files. - **Why the change was made:** - To introduce a clear `app/` directory hierarchy for core, common, and proprietary modules, improving organization and maintainability. - To ensure continuous integration and Docker builds continue to work seamlessly with the reorganized structure. - To automate OpenAPI documentation generation as part of the CI pipeline. --- ## Checklist ### General - [x] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [x] I have read the [Stirling-PDF Developer Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/DeveloperGuide.md) (if applicable) - [ ] I have read the [How to add new languages to Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md) (if applicable) - [x] I have performed a self-review of my own code - [x] My changes generate no new warnings ### Documentation - [ ] I have updated relevant docs on [Stirling-PDF's doc repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/) (if functionality has heavily changed) - [ ] I have read the section [Add New Translation Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/HowToAddNewLanguage.md#add-new-translation-tags) (for new translation tags only) ### UI Changes (if applicable) - [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR) ### Testing (if applicable) - [ ] I have tested my changes locally. Refer to the [Testing Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/devGuide/DeveloperGuide.md#6-testing) for more details.	2025-07-14 20:53:11 +01:00
3 people	dc6823d7ba	exception handling and exception improvements (#3858) ... # Description of Changes This pull request introduces several improvements to enhance error handling, internationalization, and documentation in the codebase. The key changes include the addition of `ExceptionUtils` and `I18nUtils` utility classes for consistent exception handling and internationalized messages, updates to documentation paths, and modifications to existing methods to integrate the new utilities. ### Error Handling Enhancements: * **Added `ExceptionUtils` utility class**: Provides standardized methods for creating and handling exceptions with internationalized error messages, including specific handling for PDF corruption, encryption issues, and other file-related errors. * **Integrated `ExceptionUtils` into `CustomPDFDocumentFactory`**: Updated `loadFromFile` and `loadFromBytes` methods to log and handle exceptions using `ExceptionUtils`, ensuring consistent error handling across PDF operations. [[1]](diffhunk://#diff-10208c1fc2e04631a8cf2a2a99b2a1160e532e75a7b840ad752f3b0130b89851R358-R363) [[2]](diffhunk://#diff-10208c1fc2e04631a8cf2a2a99b2a1160e532e75a7b840ad752f3b0130b89851R375-R381) * **Updated `FileToPdf` to use `ExceptionUtils`**: Replaced direct exception throwing with `ExceptionUtils.createHtmlFileRequiredException` for unsupported file formats. ### Internationalization Improvements: * **Added `I18nUtils` utility class**: Centralized access to Spring's `MessageSource` for retrieving localized messages, enabling consistent internationalization across the application. ### Documentation Updates: * **Updated documentation paths in `CONTRIBUTING.md` and `README.md`**: Changed paths to reference the new `devGuide` folder for developer documentation and translation guides. [[1]](diffhunk://#diff-eca12c0a30e25b4b46522ebf89465a03ba72a03f540796c979137931d8f92055L28-R28) [[2]](diffhunk://#diff-eca12c0a30e25b4b46522ebf89465a03ba72a03f540796c979137931d8f92055L40-R51) [[3]](diffhunk://#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5L171-L174) --- ## Checklist ### General - [ ] I have read the [Contribution Guidelines](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/CONTRIBUTING.md) - [ ] I have read the [Stirling-PDF Developer Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md) (if applicable) - [ ] I have read the [How to add new languages to Stirling-PDF](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/HowToAddNewLanguage.md) (if applicable) - [ ] I have performed a self-review of my own code - [ ] My changes generate no new warnings ### Documentation - [ ] I have updated relevant docs on [Stirling-PDF's doc repo](https://github.com/Stirling-Tools/Stirling-Tools.github.io/blob/main/docs/) (if functionality has heavily changed) - [ ] I have read the section [Add New Translation Tags](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/HowToAddNewLanguage.md#add-new-translation-tags) (for new translation tags only) ### UI Changes (if applicable) - [ ] Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR) ### Testing (if applicable) - [ ] I have tested my changes locally. Refer to the [Testing Guide](https://github.com/Stirling-Tools/Stirling-PDF/blob/main/DeveloperGuide.md#6-testing) for more details. --------- Co-authored-by: a <a>	2025-07-02 16:51:45 +01:00