[Backend] SurgeriesService.savePhoto is an unimplemented stub

[llinsss]

Location: backend/src/modules/surgeries/surgeries.service.ts (around lines 66-69)

Problem:
savePhoto() returns a hardcoded placeholder path string instead of actually handling file storage. Any caller relying on this for real photo uploads will silently get a fake path instead of a stored file (or fail later when something tries to fetch the photo from that fake path).

Why it matters:
Looks complete from the API surface but doesn't work, which is worse than an explicit 'not implemented' error — it can fail silently downstream.

Suggested fix:

• Implement actual file persistence using the existing upload/storage service used by other modules (e.g. src/modules/upload, src/modules/storage), following the same pattern.

Acceptance criteria:

• Uploaded surgery photos are actually stored and retrievable.
• A test covers the upload + retrieval path.

[Listoncrypt]

@Listoncrypt has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello, I would love to take on this issue and expect a PR within a few hours.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Listoncrypt to this issue.

[AlphaMaleBaDI]

@AlphaMaleBaDI has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I will implement actual file persistence for surgery photos in SurgeriesService.savePhoto.

To deliver a pristine, 100% compliant backend fix matching all stated acceptance criteria, I plan to:

• Review backend/src/modules/surgeries/surgeries.service.ts to replace the hardcoded placeholder path string inside savePhoto() with legitimate file handling.
• Integrate the existing storage or upload infrastructure (such as src/modules/upload or src/modules/storage) following the established pattern across other functional modules to ensure consistency.
• Guarantee that uploaded surgery photos are successfully stored, accurately mapped, and reliably retrievable by downstream services to eliminate silent failures.
• Implement a comprehensive integration test covering both the photo upload and subsequent retrieval execution paths to ensure the loop remains unbroken.

Since my local workspace is perfectly calibrated for NestJS/TypeScript backend services, multi-part file streaming, and storage pipeline architectures, I can jump straight into the service logic and submit a highly polished PR immediately. Ready to lock it in!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @AlphaMaleBaDI to this issue.

[1sraeliteX]

@1sraeliteX has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I'm interested in this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @1sraeliteX to this issue.