Skip to content

chore: release 12.0.2 #137

chore: release 12.0.2

chore: release 12.0.2 #137

Triggered via push November 22, 2024 19:21
Status Success
Total duration 3m 16s
Artifacts

ci.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
lint: example/src/components/ScreenBody.tsx#L8
Inline style: { flex: 1, alignItems: 'center', padding: 20 }
lint: example/src/screens/HomeScreen.tsx#L13
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 “HomeScreen” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true
lint: example/src/screens/HomeScreen.tsx#L18
Unexpected alert
lint: example/src/screens/HomeScreen.tsx#L23
Unexpected alert
lint: example/src/screens/HomeScreen.tsx#L36
Inline style: { rowGap: 10 }
lint: example/src/screens/HomeScreen.tsx#L37
Inline style: { margin: 15 }
lint: example/src/screens/TabScreenWithButtons.tsx#L21
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 “TabScreenWithButtons” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true
lint: example/src/screens/TabScreenWithButtons.tsx#L32
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 “TabScreenWithButtons” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true