fix: resolve eslint errors in AuthContext and test file #5
Annotations
2 errors and 1 warning
|
Run tests
Process completed with exit code 1.
|
|
Run tests:
frontend/src/test/ErrorBoundary.test.tsx#L37
TestingLibraryElementError: Unable to find an element with the text: Test crash. This could be because the text is broken up by multiple elements. In this case, you can provide a function for your text matcher to make your matcher more flexible.
Ignored nodes: comments, script, style
<body>
<div>
<div
class="page"
style="text-align: center; padding-top: 80px;"
>
<h1>
Something went wrong
</h1>
<p
class="text-muted"
style="margin: 12px 0px 20px;"
>
An unexpected error occurred. Please try again.
</p>
<button
class="btn btn-primary"
>
Go to Dashboard
</button>
</div>
</div>
</body>
❯ Object.getElementError node_modules/@testing-library/dom/dist/config.js:37:19
❯ node_modules/@testing-library/dom/dist/query-helpers.js:76:38
❯ node_modules/@testing-library/dom/dist/query-helpers.js:52:17
❯ node_modules/@testing-library/dom/dist/query-helpers.js:95:19
❯ src/test/ErrorBoundary.test.tsx:37:19
|
|
Complete job
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Loading