mirror of
https://github.com/arsvendg/Stirling-PDF.git
synced 2026-07-16 11:23:10 +02:00
# Description of Changes Closes: #5752 <!-- 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. Signed-off-by: Balázs Szücs <[email protected]>
47 lines
1.2 KiB
TypeScript
47 lines
1.2 KiB
TypeScript
/**
|
|
* API service for form-related backend calls.
|
|
*/
|
|
import apiClient from '@app/services/apiClient';
|
|
import type { FormField } from '@proprietary/tools/formFill/types';
|
|
|
|
/**
|
|
* Fetch form fields with coordinates from the backend.
|
|
* Calls POST /api/v1/form/fields-with-coordinates
|
|
*/
|
|
export async function fetchFormFieldsWithCoordinates(
|
|
file: File | Blob
|
|
): Promise<FormField[]> {
|
|
const formData = new FormData();
|
|
formData.append('file', file);
|
|
|
|
const response = await apiClient.post<FormField[]>(
|
|
'/api/v1/form/fields-with-coordinates',
|
|
formData
|
|
);
|
|
return response.data;
|
|
}
|
|
|
|
/**
|
|
* Fill form fields and get back a filled PDF blob.
|
|
* Calls POST /api/v1/form/fill
|
|
*/
|
|
export async function fillFormFields(
|
|
file: File | Blob,
|
|
values: Record<string, string>,
|
|
flatten: boolean = false
|
|
): Promise<Blob> {
|
|
const formData = new FormData();
|
|
formData.append('file', file);
|
|
formData.append(
|
|
'data',
|
|
new Blob([JSON.stringify(values)], { type: 'application/json' })
|
|
);
|
|
formData.append('flatten', String(flatten));
|
|
|
|
const response = await apiClient.post('/api/v1/form/fill', formData, {
|
|
responseType: 'blob',
|
|
});
|
|
return response.data;
|
|
}
|
|
|