- 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.
- 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.
