[WIP] Connect Categories With Main Page and Adding Categories #207
Anthonyp0329lint-check.yml
on: pull_request
Backend lint and style check
13s
Admin portal frontend lint and style check
23s
Annotations
12 warnings
|
Backend lint and style check
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Admin portal frontend lint and style check
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Admin portal frontend lint and style check:
admin-portal-frontend/src/app/category/page.tsx#L7
Using exported name 'PageContainer' as identifier for default export
|
|
Admin portal frontend lint and style check:
admin-portal-frontend/src/app/components/CategoryContainer.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
|
|
Admin portal frontend lint and style check:
admin-portal-frontend/src/app/components/CategoryContainer.tsx#L84
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/CategoryPopup.tsx#L26
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
|
|
Admin portal frontend lint and style check:
admin-portal-frontend/src/app/components/VerticalNavBar.tsx#L7
`next/link` import should occur before import of `react`
|