test:stablize swaps e2e #33907
Annotations
2 errors and 12 warnings
|
Run yarn lint:
e2e/pages/TokenOverview.js#L38
'waitFor' is not defined
|
|
Run yarn lint
Process completed with exit code 1.
|
|
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Run yarn lint:
app/actions/onboarding/index.ts#L28
Newline required at end of file but not found
|
|
Run yarn lint:
app/component-library/components-temp/Contracts/ContractBoxBase/ContractBoxBase.tsx#L42
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 “ContractBoxBase” and pass data as props
|
|
Run yarn lint:
app/components/Nav/App/index.js#L548
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 “App” and pass data as props
|
|
Run yarn lint:
app/components/Nav/App/index.js#L562
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 “App” and pass data as props
|
|
Run yarn lint:
app/components/Nav/App/index.js#L701
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 “App” and pass data as props
|
|
Run yarn lint:
app/components/Nav/App/index.js#L722
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 “App” and pass data as props
|
|
Run yarn lint:
app/components/Nav/App/index.js#L732
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 “App” and pass data as props
|
|
Run yarn lint:
app/components/Nav/App/index.js#L746
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 “App” and pass data as props
|
|
Run yarn lint:
app/components/Nav/App/index.js#L756
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 “App” and pass data as props
|
|
Run yarn lint:
app/components/Nav/App/index.js#L763
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 “App” and pass data as props
|
|
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "coverage", "coverage-1", "coverage-10", "coverage-2", "coverage-3", "coverage-4", "coverage-5", "coverage-6", "coverage-7", "coverage-8", "coverage-9".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
Loading