fix: add getItemLayout to FlatLists for virtualization performance #521
oluwaseyi1996-netizenAnnotations
10 errors and 11 warnings
|
ci:
src/__tests__/services/cacheWarming.test.ts#L4
Parse errors in imported module '../../store': ',' expected. (96:11)
|
|
ci:
src/__tests__/services/auth.test.ts#L6
Parse errors in imported module '../../store': ',' expected. (96:11)
|
|
ci:
components/ui/collapsible.tsx#L8
Parse errors in imported module '@/store': ',' expected. (96:11)
|
|
ci:
components/parallax-scroll-view.tsx#L13
Parse errors in imported module '@/store': ',' expected. (96:11)
|
|
ci:
app/settings.tsx#L6
Parse errors in imported module '@/store': ',' expected. (96:11)
|
|
ci:
app/profile/[userId].tsx#L5
Parse errors in imported module '@/store': ',' expected. (96:11)
|
|
ci:
app/_layout.tsx#L21
Parse errors in imported module '../src/store': ',' expected. (96:11)
|
|
ci:
app/(tabs)/profile.tsx#L4
Parse errors in imported module '@/store': ',' expected. (96:11)
|
|
ci:
app/(tabs)/dashboard.tsx#L11
Parse errors in imported module '@/store': ',' expected. (96:11)
|
|
ci:
app/(tabs)/_layout.tsx#L8
Parse errors in imported module '@/store': ',' expected. (96:11)
|
|
ci
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/checkout@v4, actions/setup-node@v4, actions/setup-python@v5. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
ci:
src/__tests__/services/auth.test.ts#L1
There should be no empty line within import group
|
|
ci:
src/__tests__/services/appUpdateService.test.ts#L10
A `require()` style import is forbidden
|
|
ci:
src/__tests__/appInit.test.ts#L22
A `require()` style import is forbidden
|
|
ci:
src/__tests__/appInit.test.ts#L17
A `require()` style import is forbidden
|
|
ci:
app/clipboard-demo.tsx#L120
Function component is not an arrow function
|
|
ci:
app/+html.tsx#L10
Function component is not an arrow function
|
|
ci:
app/(tabs)/_layout.tsx#L51
Do not define components during render. React will see a new component type on every render and destroy the entire subtree’s DOM nodes and state (https://reactjs.org/docs/reconciliation.html#elements-of-different-types). Instead, move this component definition out of the parent component “TabLayout” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true
|
|
ci:
app/(tabs)/_layout.tsx#L44
Do not define components during render. React will see a new component type on every render and destroy the entire subtree’s DOM nodes and state (https://reactjs.org/docs/reconciliation.html#elements-of-different-types). Instead, move this component definition out of the parent component “TabLayout” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true
|
|
ci:
app/(tabs)/_layout.tsx#L35
Do not define components during render. React will see a new component type on every render and destroy the entire subtree’s DOM nodes and state (https://reactjs.org/docs/reconciliation.html#elements-of-different-types). Instead, move this component definition out of the parent component “TabLayout” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true
|
|
ci:
app/(tabs)/_layout.tsx#L28
Do not define components during render. React will see a new component type on every render and destroy the entire subtree’s DOM nodes and state (https://reactjs.org/docs/reconciliation.html#elements-of-different-types). Instead, move this component definition out of the parent component “TabLayout” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true
|