feat(routesF): add roman numeral validator #950
Merged
Annotations
10 errors and 11 warnings
|
Lint code:
app/api/admin/feature-flags/route.ts#L78
Expected { after 'if' condition
|
|
Lint code:
app/api/admin/feature-flags/route.ts#L75
Expected { after 'if' condition
|
|
Lint code:
app/api/admin/feature-flags/route.ts#L69
Expected { after 'if' condition
|
|
Lint code:
app/api/admin/feature-flags/route.ts#L57
Expected { after 'if' condition
|
|
Lint code:
app/api/admin/feature-flags/route.ts#L54
Expected { after 'if' condition
|
|
Lint code:
app/api/admin/feature-flags/route.ts#L48
Expected { after 'if' condition
|
|
Lint code:
app/api/admin/feature-flags/route.ts#L40
Expected { after 'if' condition
|
|
Lint code:
app/api/admin/feature-flags/route.ts#L37
Expected { after 'if' condition
|
|
Lint code:
app/api/admin/feature-flags/route.ts#L29
Expected { after 'if' condition
|
|
Lint code:
app/api/admin/feature-flags/route.ts#L17
Expected { after 'if' condition
|
|
Complete job
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 16th, 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/
|
|
Lint code:
app/[username]/clips/page.tsx#L301
Unexpected console statement
|
|
Lint code:
app/[username]/clips/page.tsx#L290
Unexpected console statement
|
|
Lint code:
app/[username]/clips/page.tsx#L135
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
|
|
Lint code:
app/[username]/clips/page.tsx#L128
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
|
|
Lint code:
app/[username]/about/page.tsx#L12
Unexpected any. Specify a different type
|
|
Lint code:
app/[username]/UsernameLayoutClient.tsx#L28
Unexpected any. Specify a different type
|
|
Lint code:
__tests__/lib/stellar/config.test.ts#L46
Unexpected console statement
|
|
Lint code:
__tests__/lib/stellar/config.test.ts#L38
Unexpected console statement
|
|
Lint code:
__tests__/lib/stellar/config.test.ts#L32
Unexpected console statement
|
|
Lint code:
__tests__/lib/stellar/config.test.ts#L26
Unexpected console statement
|
background
wait
wait-all
cancel
Loading