Redid the new court tagger with better UI #41
krish1925Annotations
3 errors and 11 warnings
|
lint:
app/timestamp-tagger/page.js#L245
'handleDownload' is assigned a value but never used
|
|
lint:
app/timestamp-tagger/page.js#L261
'handleCopyColumns' is assigned a value but never used
|
|
lint
Process completed with exit code 1.
|
|
lint
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
|
lint:
app/DataProvider.js#L110
React Hook useCallback has a missing dependency: 'fetchMatches'. Either include it or remove the dependency array
|
|
lint:
app/components/Dashboard.js#L122
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
|
|
lint:
app/components/DashboardTile.js#L52
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
|
|
lint:
app/components/DashboardTile.js#L101
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
|
|
lint:
app/components/ExtendedList.js#L89
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
|
|
lint:
app/components/ExtendedList.js#L89
img elements must have an alt prop, either with meaningful text, or an empty string for decorative images
|
|
lint:
app/components/MatchTiles.js#L70
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
|
|
lint:
app/components/MatchTiles.js#L119
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
|
|
lint:
app/components/PlayerProfileHeader.js#L30
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
|
|
lint:
app/components/PointsList.js#L71
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
|