Ca adjustment

[JessB2000]

No description provided.

In general, to fix this class of problem you must validate the runtime type of any user-controlled value before calling string methods or using it in string concatenation, and reject or sanitize unexpected types (like arrays or objects). For query parameters in Express/NestJS this usually means: if the value is not a string, return a 400 Bad Request.

Here, the best fix with minimal behavioral change is:

1. In MinioClientController, ensure that objectKey from @Query('key') is a single string and not an array or other type. If it is not a string or is empty, throw BadRequestException. Because all existing service methods already assume a string, doing this at the controller boundary centralizes validation and avoids needing extra checks deeper in the service.
2. Optionally, we can keep MinioClientService.resolveObjectKey as-is, because after the controller fixes, it will only receive strings. However, for extra safety, we can make resolveObjectKey robust by guarding its includes call with a simple string check and throwing a BadRequestException for unexpected types. This ensures future callers within the service cannot accidentally pass a non-string.

Concretely:

• In src/minio/minio.controller.ts, update viewDocument to:
  • Check typeof objectKey !== 'string' and reject with BadRequestException.
  • Keep the existing “empty” check, but now it runs only for valid strings.
• Add a similar runtime type check to getPresignedUrl.
• In src/minio/minio.service.ts, update resolveObjectKey to:
  • Throw BadRequestException if typeof key !== 'string' or key is empty-ish.
  • Only then call key.includes('/') and build paths.

No new methods are strictly required beyond using the already imported BadRequestException. There are no new imports needed.