fix: resolve logic error in image preview #84
+36
−119
Merged
Annotations
6 warnings
|
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 2nd, 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/
|
|
🔍 Run linter:
components/object/preview-modal.tsx#L254
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
|
|
🔍 Run linter:
components/object/list.tsx#L315
React Hook React.useMemo has a missing dependency: 'onPreview'. Either include it or remove the dependency array. If 'onPreview' changes too often, find the parent component that defines it and wrap that definition in useCallback
|
|
🔍 Run linter:
components/object/info.tsx#L223
The ref value 'previewParamSyncTimerRef.current' will likely have changed by the time this effect cleanup function runs. If this ref points to a node rendered by React, copy 'previewParamSyncTimerRef.current' to a variable inside the effect, and use that variable in the cleanup function
|
|
🔍 Run linter:
app/(dashboard)/browser/content.tsx#L27
'previewKey' is assigned a value but never used
|
|
🔍 Run linter:
app/(dashboard)/browser/content.tsx#L27
'preview' is assigned a value but never used
|
Loading