Categories page #180
Anthonyp0329lint-check.yml
on: pull_request
Backend lint and style check
13s
Frontend lint and style check
33s
Admin portal frontend lint and style check
22s
Annotations
2 errors and 13 warnings
|
Admin portal frontend lint and style check:
admin-portal-frontend/src/app/components/SearchBar.tsx#L13
Unsafe assignment of an `any` value
|
|
Admin portal frontend lint and style check
Process completed with exit code 1.
|
|
Frontend lint and style check
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Frontend lint and style check:
dfm-sideline-sidekick-app/download/connection/checkConnection.ts#L7
Caution: `NetInfo` also has a named export `fetch`. Check if you meant to write `import {fetch} from '@react-native-community/netinfo'` instead
|
|
Backend lint and style check
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Admin portal frontend lint and style check
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
Admin portal frontend lint and style check:
admin-portal-frontend/src/app/all-page/page.tsx#L6
Using exported name 'PageContainer' as identifier for default export
|
|
Admin portal frontend lint and style check:
admin-portal-frontend/src/app/all-page/page.tsx#L103
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
|
|
Admin portal frontend lint and style check:
admin-portal-frontend/src/app/components/CategoryContainer.tsx#L72
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
|
|
Admin portal frontend lint and style check:
admin-portal-frontend/src/app/components/CategoryContainer.tsx#L75
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
|
|
Admin portal frontend lint and style check:
admin-portal-frontend/src/app/components/DeletePopup.tsx#L25
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
|
|
Admin portal frontend lint and style check:
admin-portal-frontend/src/app/components/PageContainer.tsx#L73
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
|
|
Admin portal frontend lint and style check:
admin-portal-frontend/src/app/components/PageContainer.tsx#L76
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
|
|
Admin portal frontend lint and style check:
admin-portal-frontend/src/app/components/Toast.tsx#L35
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
|
|
Admin portal frontend lint and style check:
admin-portal-frontend/src/app/components/Toast.tsx#L38
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
|