ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636

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 “ButtonScreen” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true

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 “TabOneScreen” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true

Inline style: { height: 5 }

'props' is already declared in the upper scope on line 33 column 18

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 “TabOneScreen” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true

Inline style: { height: 5 }

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 “TabOneScreen” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true

Inline style: { height: 5 }

'no-eval' rule is disabled but never reported