Skip to content

Eslint config 9.0 migration #222

Eslint config 9.0 migration

Eslint config 9.0 migration #222

Re-run triggered September 5, 2024 18:01
Status Failure
Total duration 34s
Artifacts

test.yaml

on: pull_request
Matrix: Unit Tests
Matrix: NPM Build
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 3 warnings
src/hooks/useFetchConfig/useFetchConfig.spec.tsx > useFetchConfig > sets the first node in the array to visible and the rest to hidden: src/hooks/useFetchConfig/useFetchConfig.spec.tsx#L85
Error: expect(received).toBeInTheDocument() received value must be an HTMLElement or an SVGElement. ❯ src/hooks/useFetchConfig/useFetchConfig.spec.tsx:85:56
Unit Tests (20)
Process completed with exit code 1.
NPM Build (20)
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/
Image Builds
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, docker/metadata-action@v4, docker/build-push-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Lint
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/