mirror of
https://github.com/Stirling-Tools/Stirling-PDF.git
synced 2025-08-24 21:29:25 +00:00
9c9acbfb5b
🔄 Dynamic Processing Strategies - Adaptive routing: Same tool uses different backend endpoints based on file analysis - Combined vs separate processing: Intelligently chooses between merge operations and individual file processing - Cross-format workflows: Enable complex conversions like "mixed files → PDF" that other tools can't handle ⚙️ Format-Specific Intelligence Each conversion type gets tailored options: - HTML/ZIP → PDF: Zoom controls (0.1-3.0 increments) with live preview - Email → PDF: Attachment handling, size limits, recipient control - PDF → PDF/A: Digital signature detection with warnings - Images → PDF: Smart combining vs individual file options File Architecture Core Implementation: ├── Convert.tsx # Main stepped workflow UI ├── ConvertSettings.tsx # Centralized settings with smart detection ├── GroupedFormatDropdown.tsx # Enhanced format selector with grouping ├── useConvertParameters.ts # Smart detection & parameter management ├── useConvertOperation.ts # Multi-strategy processing logic └── Settings Components: ├── ConvertFromWebSettings.tsx # HTML zoom controls ├── ConvertFromEmailSettings.tsx # Email attachment options ├── ConvertToPdfaSettings.tsx # PDF/A with signature detection ├── ConvertFromImageSettings.tsx # Image PDF options └── ConvertToImageSettings.tsx # PDF to image options Utility Layer Utils & Services: ├── convertUtils.ts # Format detection & endpoint routing ├── fileResponseUtils.ts # Generic API response handling └── setupTests.ts # Enhanced test environment with crypto mocks Testing & Quality Comprehensive Test Coverage Test Suite: ├── useConvertParameters.test.ts # Parameter logic & smart detection ├── useConvertParametersAutoDetection.test.ts # File type analysis ├── ConvertIntegration.test.tsx # End-to-end conversion workflows ├── ConvertSmartDetectionIntegration.test.tsx # Mixed file scenarios ├── ConvertE2E.spec.ts # Playwright browser tests ├── convertUtils.test.ts # Utility function validation └── fileResponseUtils.test.ts # API response handling Advanced Test Features - Crypto API mocking: Proper test environment for file hashing - File.arrayBuffer() polyfills: Complete browser API simulation - Multi-file scenario testing: Complex batch processing validation - CI/CD integration: Vitest runs in GitHub Actions with proper artifacts --------- Co-authored-by: Connor Yoh <connor@stirlingpdf.com> Co-authored-by: Anthony Stirling <77850077+Frooodle@users.noreply.github.com>
37 lines
1.3 KiB
TypeScript
37 lines
1.3 KiB
TypeScript
/**
|
|
* Generic utility functions for handling file responses from API endpoints
|
|
*/
|
|
|
|
/**
|
|
* Extracts filename from Content-Disposition header
|
|
* @param contentDisposition - Content-Disposition header value
|
|
* @returns Filename if found, null otherwise
|
|
*/
|
|
export const getFilenameFromHeaders = (contentDisposition: string = ''): string | null => {
|
|
const match = contentDisposition.match(/filename[^;=\n]*=((['"]).*?\2|[^;\n]*)/);
|
|
if (match && match[1]) {
|
|
return match[1].replace(/['"]/g, '');
|
|
}
|
|
return null;
|
|
};
|
|
|
|
/**
|
|
* Creates a File object from API response using the filename from headers
|
|
* @param responseData - The response data (blob/arraybuffer/string)
|
|
* @param headers - Response headers object
|
|
* @param fallbackFilename - Filename to use if none provided in headers
|
|
* @returns File object
|
|
*/
|
|
export const createFileFromApiResponse = (
|
|
responseData: any,
|
|
headers: any,
|
|
fallbackFilename: string
|
|
): File => {
|
|
const contentType = headers?.['content-type'] || 'application/octet-stream';
|
|
const contentDisposition = headers?.['content-disposition'] || '';
|
|
|
|
const filename = getFilenameFromHeaders(contentDisposition) || fallbackFilename;
|
|
const blob = new Blob([responseData], { type: contentType });
|
|
|
|
return new File([blob], filename, { type: contentType });
|
|
}; |