New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

231 timestamp shortcuts jump for tagging #266

Open

krish1925 wants to merge 2 commits into development from 231-timestamp-shortcuts-jump-for-tagging

Open

231 timestamp shortcuts jump for tagging #266

Formatting improved, default zero value added

Annotations

11 warnings

ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

Run ESLint: app/DataProvider.js#L110

React Hook useCallback has a missing dependency: 'fetchMatches'. Either include it or remove the dependency array

Run ESLint: 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

Run ESLint: 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

Run ESLint: 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

Run ESLint: 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

Run ESLint: app/components/ExtendedList.js#L89

img elements must have an alt prop, either with meaningful text, or an empty string for decorative images

Run ESLint: 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

Run ESLint: 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

Run ESLint: 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

Run ESLint: 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