Error management if a source is unreachable

Created on 18 July 2024, 5 months ago

Problem/Motivation

I made a test while working on 📌 Use the production URL for Drupal.org endpoint Fixed to test what would happen if the endpoint goes down. Nothing happens on the front-end, it just displays 0 results. On the backend, an error to the watchdog is added.

Maybe we can inform the users that this is not a "there is no data" situation, but a "something is wrong" situation.

Steps to reproduce

Change the endpoint for a non-existent URL (to simulate the endpoint not being reachable), clear caches and use Project Browser.

Proposed resolution

Add some degree of information to tell the two situations apart.

I made a test on the other issue in this commit: https://git.drupalcode.org/issue/project_browser-3462173/-/commit/e0153c...

The idea is that totalResults could be set to -1 in these cases and we could display something in the front end. As that was opinionated and did not change styles to convey an error, I decided to revert the commit and create this follow up issue.

📌 Task
Status

Active

Version

2.0

Component

Code

Created by

🇪🇸Spain fjgarlin

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024