In some cases, the server may return 404 "there is no content". This says something like "No data found".
However, there are error cases for bad data or failure to process that need to be made clear to the viewer that somewhere in the supply chain there is a problem, so they do not mistake it for a "still loading" or "nothing found" situation.
Use case
Server serves 400 or 401 or 405+
contents returned by server do not parse
etc
Proposed solution
Simple and delightfu error message shown in body of widget - needs mockup.
It is NOT necessary to display the exact error message received on screen, especially if that is a huge IO-TS parsing error. Can dump these to console.
Additional information
Provide any additional information that might be helpful in understanding the feature request.
ships
commented
8 months ago
Feature Request
Packages to improve:
Description
In some cases, the server may return 404 "there is no content". This says something like "No data found".
However, there are error cases for bad data or failure to process that need to be made clear to the viewer that somewhere in the supply chain there is a problem, so they do not mistake it for a "still loading" or "nothing found" situation.
Use case
Proposed solution
Simple and delightfu error message shown in body of widget - needs mockup.
It is NOT necessary to display the exact error message received on screen, especially if that is a huge IO-TS parsing error. Can dump these to console.
Additional information
Provide any additional information that might be helpful in understanding the feature request.