Skip to content

Fixed all existing type errors #393

Fixed all existing type errors

Fixed all existing type errors #393

Triggered via pull request February 21, 2025 23:20
Status Failure
Total duration 1m 47s
Artifacts

main.yml

on: pull_request
Matrix: linting
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 5 warnings
linting (20): my-turborepo/packages/auth/src/config.ts#L38
Expected an error object to be thrown
linting (20): my-turborepo/packages/api/src/router/application.ts#L26
Unexpected any. Specify a different type
linting (20): my-turborepo/packages/api/src/router/application.ts#L42
Unsafe assignment of an `any` value
linting (20): my-turborepo/packages/api/src/router/application.ts#L42
Unsafe call of a(n) `any` typed value
linting (20): my-turborepo/packages/api/src/router/application.ts#L42
Unsafe call of a(n) `any` typed value
linting (20): my-turborepo/packages/api/src/router/application.ts#L42
Unsafe call of a(n) `any` typed value
linting (20): my-turborepo/packages/api/src/router/application.ts#L42
Unsafe call of a(n) `any` typed value
linting (20): my-turborepo/packages/api/src/router/application.ts#L42
Unsafe call of a(n) `any` typed value
linting (20): my-turborepo/packages/api/src/router/application.ts#L42
Unsafe call of a(n) `any` typed value
linting (20): my-turborepo/packages/api/src/router/application.ts#L42
Unsafe call of a(n) `any` typed value
linting (20)
Cache not found for keys: node-cache-Linux-x64-pnpm-6ab32b57bd4e101052a126b178ba649e21d271f5dfaf1de0b3fb965a4a82d8dd
linting (20): my-turborepo/apps/nextjs/src/app/_components/genericCombobox.tsx#L80
React Hook useMemo has missing dependencies: 'filter' and 'isDebouncing'. Either include them or remove the dependency array
linting (20): my-turborepo/apps/nextjs/src/app/apply/application/page.tsx#L11
Prevent client components from being async functions. See: https://nextjs.org/docs/messages/no-async-client-component
linting (20): my-turborepo/apps/nextjs/src/app/page.tsx#L81
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
linting (20): my-turborepo/apps/nextjs/src/app/schedule/EventAlertPopup.tsx#L33
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element