feat(routes-f): add queue, archives, leaderboards, and clip collections #177
Jay-Peter-EgemasiAnnotations
10 errors and 11 warnings
|
quality:
app/api/routes-f/clips/submit/[id]/route.ts#L51
Expected { after 'if' condition
|
|
quality:
app/api/routes-f/clips/submit/[id]/route.ts#L46
Expected { after 'if' condition
|
|
quality:
app/api/routes-f/clips/captions/_lib/db.ts#L30
Expected { after 'if' condition
|
|
quality:
app/api/routes-f/clips/captions/_lib/db.ts#L27
Expected { after 'if' condition
|
|
quality:
app/api/routes-f/audit/route.ts#L67
Expected { after 'if' condition
|
|
quality:
app/api/routes-f/announcements/route.ts#L51
Expected { after 'if' condition
|
|
quality:
app/api/routes-f/announcements/route.ts#L15
Expected { after 'if' condition
|
|
quality:
app/api/routes-f/announcements/[id]/route.ts#L38
Expected { after 'if' condition
|
|
quality:
app/api/routes-f/announcements/[id]/route.ts#L16
Expected { after 'if' condition
|
|
quality:
app/[username]/watch/page.tsx#L58
Expected { after 'if' condition
|
|
quality
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
quality:
app/[username]/clips/page.tsx#L284
Unexpected console statement
|
|
quality:
app/[username]/clips/page.tsx#L273
Unexpected console statement
|
|
quality:
app/[username]/clips/page.tsx#L132
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
quality:
app/[username]/clips/page.tsx#L125
Using `<img>` could result in slower LCP and higher bandwidth. Consider using `<Image />` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element
|
|
quality:
app/[username]/about/page.tsx#L12
Unexpected any. Specify a different type
|
|
quality:
app/[username]/UsernameLayoutClient.tsx#L29
Unexpected any. Specify a different type
|
|
quality:
__tests__/lib/stellar/config.test.ts#L46
Unexpected console statement
|
|
quality:
__tests__/lib/stellar/config.test.ts#L38
Unexpected console statement
|
|
quality:
__tests__/lib/stellar/config.test.ts#L32
Unexpected console statement
|
|
quality:
__tests__/lib/stellar/config.test.ts#L26
Unexpected console statement
|