Skip to content

feat: Add Nfd into search #715

feat: Add Nfd into search

feat: Add Nfd into search #715

Triggered via pull request October 2, 2024 02:41
Status Failure
Total duration 2m 10s
Artifacts

pr.yaml

on: pull_request
Run PR checks  /  node-ci
1m 59s
Run PR checks / node-ci
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
src/features/search/components/search.test.tsx > search > when search results have been returned > and the 'Account' result is selected > should navigate to the account page: src/features/nfd/data/nfd-result.ts#L20
TestingLibraryElementError: Unable to find an element with the placeholder text of: Search by ID or Address (Ctrl+K) Ignored nodes: comments, script, style <body> <div> <h2> Unexpected Application Error! </h2> <h3 style="font-style: italic;" > Nfd is not found </h3> <pre style="padding: 0.5rem; background-color: rgba(200, 200, 200, 0.5);" > Error: Nfd is not found at getReverseNfdResult (/home/runner/work/algokit-lora/algokit-lora/src/features/nfd/data/nfd-result.ts:20:11) at processTicksAndRejections (node:internal/process/task_queues:95:5) </pre> <p> 💿 Hey developer 👋 </p> <p> You can provide a way better UX than this when your app throws errors by providing your own <code style="padding: 2px 4px; background-color: rgba(200, 200, 200, 0.5);" > ErrorBoundary </code> or <code style="padding: 2px 4px; background-color: rgba(200, 200, 200, 0.5);" > errorElement </code> prop on your route. </p> </div> </body> Ignored nodes: comments, script, style <html class="light" > <head /> <body> <div> <h2> Unexpected Application Error! </h2> <h3 style="font-style: italic;" > Nfd is not found </h3> <pre style="padding: 0.5rem; background-color: rgba(200, 200, 200, 0.5);" > Error: Nfd is not found at getReverseNfdResult (/home/runner/work/algokit-lora/algokit-lora/src/features/nfd/data/nfd-result.ts:20:11) at processTicksAndRejections (node:internal/process/task_queues:95:5) </pre> <p> 💿 Hey developer 👋 </p> <p> You can provide a way better UX than this when your app throws errors by providing your own <code style="padding: 2px 4px; background-color: rgba(200, 200, 200, 0.5);" > ErrorBoundary </code> or <code style="padding: 2px 4px; background-color: rgba(200, 200, 200, 0.5);" > errorElement </code> prop on your route. </p> </div> </body> </html> ❯ getReverseNfdResult src/features/nfd/data/nfd-result.ts:20:11 ❯ Module.waitFor node_modules/@testing-library/dom/dist/wait-for.js:163:27 ❯ assertion src/features/search/components/search.test.tsx:82:19 ❯ Module.executeComponentTest src/tests/test-component.tsx:11:9 ❯ src/features/search/components/search.test.tsx:79:16
Run PR checks / node-ci
Process completed with exit code 1.
Run PR checks / node-ci
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/