Currently fetchEndpoint() reports all API failures as “not found,” even for network errors, server errors, or malformed API responses.
Adding typed/classified error handling so only 404s use the not-found message, while 5xx, network, and unexpected-data failures get
accurate user-facing errors.
Currently
fetchEndpoint()reports all API failures as “not found,” even for network errors, server errors, or malformed API responses.Adding typed/classified error handling so only 404s use the not-found message, while 5xx, network, and unexpected-data failures get
accurate user-facing errors.