Skip to content
CI

define and use custom parseLinkHeader function in pagination #321

Sign in to view logs

define and use custom parseLinkHeader function in pagination

define and use custom parseLinkHeader function in pagination #321

Triggered via pull request May 8, 2024 23:54
@shellyearshellyear
synchronize #155
akaene:fix/pagination
Status Failure
Total duration 1m 21s
Artifacts –

merge-to-protected.yml

on: pull_request
build
1m 11s
build
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 2 warnings
tests/__tests__/components/Pagination.spec.jsx > Pagination > renders pagination with first, previous and next button: tests/__tests__/components/Pagination.spec.jsx#L21
AssertionError: expected 3 to deeply equal 4 - Expected + Received - 4 + 3 ❯ tests/__tests__/components/Pagination.spec.jsx:21:23
build
Process completed with exit code 1.
build
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/setup-node@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/