Web migration #53
Triggered via pull request
June 3, 2026 11:30
ShantKhatri
reopened
#466
Status
Failure
Total duration
48s
Artifacts
–
ci.yml
on: pull_request_target
Annotations
22 errors and 3 warnings
|
mobile-ci
Process completed with exit code 1.
|
|
mobile-ci
Process completed with exit code 1.
|
|
mobile-ci:
apps/mobile/src/screens/TeamsScreen.tsx#L3
'FlatList' is defined but never used
|
|
mobile-ci:
apps/mobile/src/screens/TeamsScreen.tsx#L1
'useCallback' is defined but never used
|
|
mobile-ci:
apps/mobile/src/screens/TeamDetailScreen.tsx#L7
'Icon' is defined but never used
|
|
mobile-ci:
apps/mobile/src/screens/ScanScreen.tsx#L107
'err' is defined but never used
|
|
mobile-ci:
apps/mobile/src/screens/EventsScreen.tsx#L1
'useCallback' is defined but never used
|
|
web-ci
Process completed with exit code 1.
|
|
web-ci
Process completed with exit code 1.
|
|
web-ci
Process completed with exit code 254.
|
|
backend-ci
Process completed with exit code 1.
|
|
backend-ci
Parameter 'link' implicitly has an 'any' type.
|
|
backend-ci
Parameter 'm' implicitly has an 'any' type.
|
|
backend-ci
Parameter 'u' implicitly has an 'any' type.
|
|
backend-ci
Parameter 'tm' implicitly has an 'any' type.
|
|
backend-ci
'error' is of type 'unknown'.
|
|
backend-ci
Property 'PrismaClientKnownRequestError' does not exist on type 'typeof Prisma'.
|
|
backend-ci
Parameter 'tx' implicitly has an 'any' type.
|
|
backend-ci
Module '"@prisma/client"' has no exported member 'TeamRole'.
|
|
backend-ci
Argument of type '(code?: number | string) => never' is not assignable to parameter of type 'NormalizedPrecedure<(code?: string | number | null | undefined) => never>'.
|
|
backend-ci
Module '"@prisma/client"' has no exported member 'TeamRole'.
|
|
backend-ci
Process completed with exit code 2.
|
|
mobile-ci:
apps/mobile/src/screens/HomeScreen.tsx#L254
Inline style: { opacity: 0 }
|
|
mobile-ci:
apps/mobile/src/navigation/MainTabs.tsx#L110
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 “TabNavigator” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true
|
|
mobile-ci:
apps/mobile/src/navigation/MainTabs.tsx#L99
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 “TabNavigator” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true
|