Feature/kevinsophia/event creator #138
jennymarAnnotations
5 errors and 11 warnings
|
Frontend check:
frontend/src/app/admin/event-creator/page.tsx#L124
'currentYear' is assigned a value but never used. Allowed unused vars must match /^_/u
|
|
Frontend check:
frontend/src/components/EventSidebar.tsx#L121
Unexpected comparison to newly constructed object. These two values can never be equal
|
|
Frontend check:
frontend/src/components/EventSidebar.tsx#L136
Unexpected comparison to newly constructed object. These two values can never be equal
|
|
Frontend check:
frontend/src/components/EventSidebar.tsx#L348
'date' is already declared in the upper scope on line 44 column 10
|
|
Frontend check
Process completed with exit code 1.
|
|
Frontend 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 check:
frontend/src/app/(web app)/newsletter/[newsletterID]/page.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
|
|
Frontend check:
frontend/src/app/(web app)/newsletter/[newsletterID]/page.tsx#L93
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
|
|
Frontend check:
frontend/src/app/(web app)/newsletter/[newsletterID]/page.tsx#L104
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
|
|
Frontend check:
frontend/src/app/(web app)/page.tsx#L93
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
|
|
Frontend check:
frontend/src/app/admin/event-creator/page.tsx#L358
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
|
|
Frontend check:
frontend/src/app/admin/mailing-list/page.tsx#L78
'handleCopyEmails' was used before it was defined
|
|
Frontend check:
frontend/src/app/admin/mailing-list/page.tsx#L78
'handleEmailHover' was used before it was defined
|
|
Frontend check:
frontend/src/app/admin/mailing-list/page.tsx#L353
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
|
|
Frontend check:
frontend/src/app/admin/newsletter-creator/page.tsx#L296
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
|
|
Frontend check:
frontend/src/app/admin/util/validateEnv.ts#L7
Member 'json' of the import declaration should be sorted alphabetically
|