Revert to state at d6fa552 (encourage wide chart types) #342
Annotations
1 error and 11 warnings
|
Run ESLint:
frontend/src/components/blocks/BlockContentRenderer.tsx#L196
React Hook "useMemo" is called conditionally. React Hooks must be called in the exact same order in every component render. Did you accidentally call a React Hook after an early return?
|
|
Check for console.log statements
Found console.log statements - consider removing for production
|
|
Run ESLint:
frontend/src/components/app/RouteLoadingSkeleton.tsx#L43
'_files' is defined but never used
|
|
Run ESLint:
frontend/src/components/app/RouteLoadingSkeleton.tsx#L43
'_text' is defined but never used
|
|
Run ESLint:
frontend/src/components/app/OnboardingModal.tsx#L506
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 ESLint:
frontend/src/components/app/MessageList.tsx#L72
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 ESLint:
frontend/src/components/app/ChatInput.tsx#L438
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 ESLint:
frontend/src/components/app/ChatInput.tsx#L51
'isPreparing' is assigned a value but never used
|
|
Run ESLint:
frontend/src/components/app/AppContentRouter.tsx#L128
React Hook useEffect has missing dependencies: 'conversation' and 'upsertConversation'. Either include them or remove the dependency array
|
|
Run ESLint:
frontend/src/app/demo/page.tsx#L376
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 ESLint:
frontend/src/app/demo/page.tsx#L305
Image elements must have an alt prop, either with meaningful text, or an empty string for decorative images
|
|
Run ESLint:
frontend/src/app/demo/page.tsx#L4
'Play' is defined but never used
|
background
wait
wait-all
cancel
Loading