- Updated ChangeEquipmentStatusCreate and ChangeEquipmentStatusEdit components to include fullWidth properties for better layout consistency.
- Added a required DateInput field for "Дата" in both ChangeEquipmentStatus forms.
- Improved EquipmentEdit component by making fields fullWidth and adding helper text for the serial number input.
- Rearranged fields in EquipmentEdit for improved user experience.
- Added a text input for "Номер" in both ChangeEquipmentStatusCreate and ChangeEquipmentStatusEdit components.
- Rearranged the order of fields in the forms for better user experience.
- Included the StatusChangeAttachmentsInput component to handle file attachments in both forms.
- Added a new component, StatusChangeAttachmentLink, to render file attachments in the ChangeEquipmentStatusList.
- Updated the rendering logic to display up to three attachment links with a count of additional attachments if more than three exist.
- Improved the overall user interface for better visibility of file attachments related to equipment status changes.
- Introduced functionality for uploading and managing attachments in the ChangeEquipmentStatus module.
- Added new endpoints for uploading and deleting attachments, as well as for downloading them.
- Updated the ChangeEquipmentStatusService to handle attachment storage and retrieval using the new storage service methods.
- Enhanced the ChangeEquipmentStatusEdit and ChangeEquipmentStatusShow components to support attachment input and display.
- Removed deprecated attachment handling from Equipment module to streamline functionality.
- Updated Prisma schema to reflect changes in attachment management.
- Renamed the main component from `App` to `ToirAdmin` for clarity.
- Integrated theme support using `useEmbeddedParentTheme` to dynamically adjust the UI based on the parent theme.
- Updated `EmbeddedActiveEquipmentPage` to utilize the new theme and improved styling for better user experience.
- Added a new utility hook `useEmbeddedParentTheme` to manage theme changes via postMessage from parent origins.
- Enhanced the `vite-env.d.ts` file to include environment variable definitions for parent origins.
- Introduced a new endpoint `GET /equipment/{id}/attachment/download` in the API for downloading equipment attachment files.
- Implemented the `downloadEquipmentAttachmentFile` function in the client to handle file downloads via the API, ensuring proper token management and blob handling.
- Updated the EquipmentAttachmentInput, EquipmentList, and EquipmentShow components to utilize the new download link, enhancing user experience by allowing direct downloads without exposing the MinIO URL.
- Added a new EquipmentAttachmentLink component to encapsulate the download link logic and improve code reusability.
- Introduced a new utility function to decode filenames from multipart uploads that may be misencoded as ISO-8859-1.
- Updated EquipmentService to utilize this function when processing file attachments, ensuring correct original file names are stored and returned.
- Added detailed error handling for S3 operations in StorageService to interpret and throw appropriate exceptions based on the response.
- Updated .env.example to clarify the S3 endpoint configuration for MinIO in Docker.
- Introduced a function to handle schema synchronization with prisma db push.
- Enhanced migration logic to fall back to db push if migration fails with P3005 error.
- Improved logging for migration processes to aid in debugging.
- Changed healthcheck command to use 'http' module for better error handling.
- Increased timeout to 10s, retries to 8, and start period to 120s to accommodate cold starts.
- Introduced DTO for file attachments with metadata (objectKey, originalFileName, contentType, sizeBytes, downloadUrl).
- Updated Equipment DTO to include an optional attachment field.
- Implemented endpoints for uploading and deleting equipment attachments.
- Enhanced Equipment service to handle file storage and retrieval using S3.
- Updated EquipmentEdit, EquipmentList, and EquipmentShow components to support file attachment input and display.
- Configured S3 settings in docker-compose and environment files.
