Files
docker-swarm-termina/frontend
Claude 442bcc623c Fix TypeScript errors in useContainerActions test
Added missing 'success: true' property to all mock ContainerActionResponse
objects in the test file. These were causing TypeScript compilation errors
during the Next.js build process (tsc --noEmit), even though Jest tests
were passing.

The ContainerActionResponse interface requires the 'success' property,
but the mocks were only providing 'message'. This caused CI builds to fail
while local Jest tests passed because Jest's TypeScript handling is more
lenient than Next.js's build-time type checking.

Fixed:
- mockApiClient.startContainer responses (2 occurrences)
- mockApiClient.stopContainer response
- mockApiClient.restartContainer response
- mockApiClient.removeContainer response

Verified:
- npx tsc --noEmit: ✓ No TypeScript errors
- npm test: ✓ All tests pass
- npm run build: ✓ Build succeeds

https://claude.ai/code/session_7d4f1b7d-7a0d-44db-b437-c76b6b61dfb2
2026-02-01 22:39:18 +00:00
..
2026-02-01 22:13:12 +00:00

This is a Next.js project bootstrapped with create-next-app.

Getting Started

First, run the development server:

npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev

Open http://localhost:3000 with your browser to see the result.

You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.

This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.

Learn More

To learn more about Next.js, take a look at the following resources:

You can check out the Next.js GitHub repository - your feedback and contributions are welcome!

Deploy on Vercel

The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.

Check out our Next.js deployment documentation for more details.