fix(logs): ensure safe access to service error in ShowDockerLogs component

- Updated the ShowDockerLogs component to use optional chaining when accessing the error property of services, preventing potential runtime errors.
- Refactored the deployApplication function to create an applicationEntity object, ensuring consistent use of serverId across repository cloning functions.
- Removed unused createEnvFile function from utils, streamlining the codebase.
This commit is contained in:
Mauricio Siu
2026-02-07 23:34:35 -06:00
parent f1d0fb95f4
commit a0d9f06a35
4 changed files with 12 additions and 27 deletions

View File

@@ -175,7 +175,7 @@ export const ShowDockerLogs = ({ appName, serverId }: Props) => {
services?.find((c) => c.containerId === containerId)?.error && (
<div className="rounded-md bg-destructive/10 border border-destructive/20 px-3 py-2 text-sm text-destructive">
<span className="font-medium">Error: </span>
{services.find((c) => c.containerId === containerId)?.error}
{services?.find((c) => c.containerId === containerId)?.error}
</div>
)}
<DockerLogs