Skip to content

Build(deps): Bump secp256k1 from 4.0.3 to 4.0.4 #4835

Build(deps): Bump secp256k1 from 4.0.3 to 4.0.4

Build(deps): Bump secp256k1 from 4.0.3 to 4.0.4 #4835

Triggered via push November 27, 2024 14:56
Status Success
Total duration 2m 26s
Artifacts

ci.yml

on: push
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
test: src/navigation/contactsNavigator/index.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 “ContactsNavigation” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true
test: src/navigation/rootNavigator/index.tsx#L60
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 “RootNavigationComponent” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true
test: src/screens/contacts/ContactDetails.tsx#L126
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 “ContactDetails” and pass data as props. If you want to allow component creation in props, set allowAsProps option to true
test: src/screens/send/TransactionForm.tsx#L140
'@typescript-eslint/no-non-null-assertion' rule is disabled but never reported