Feature/navigation

[KelianHalleray]

PR Type

Summary

Description

What's Changed

• [ ]
• [ ]
• [ ]

Screen

Will

---

[qodo-code-review]

CI Feedback 🧐

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: Lint, format, typecheck, build

Failed stage: Lint [❌]

Failed test name: ""

Failure summary: The action failed during the ESLint step because lint warnings are treated as failures (--max-warnings 0). - ESLint reported 1 warning in src/components/dashboard/camera-feed.tsx at 32:15 from rule @next/next/no-img-element (using instead of Next.js ). - Since the workflow allows a maximum of 0 warnings, ESLint exited with code 1 (ESLint found too many warnings (maximum: 0).).

Relevant error logs: 1: ##[group]Runner Image Provisioner 2: Hosted Compute Agent ... 231: + jsdom 25.0.1 232: + lint-staged 15.5.2 233: + prettier 3.8.1 234: + tailwindcss 4.2.1 235: + typescript 5.9.3 236: + vitest 2.1.9 237: Done in 9.9s 238: ##[group]Run pnpm exec eslint . --max-warnings 0 239: �[36;1mpnpm exec eslint . --max-warnings 0�[0m 240: shell: /usr/bin/bash -e {0} 241: env: 242: PNPM_HOME: /home/runner/setup-pnpm/node_modules/.bin 243: ##[endgroup] 244: /home/runner/work/robot-front/robot-front/src/components/dashboard/camera-feed.tsx 245: ##[warning] 32:15 warning Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element 246: ✖ 1 problem (0 errors, 1 warning) 247: ESLint found too many warnings (maximum: 0). 248: ##[error]Process completed with exit code 1. 249: Post job cleanup.

[damnthonyy]

increase --max-warnings to 4 like and its good. Its just a warning