feat: error handling for HttpErrorResponse

[dianasavvatina]

Proposed changes

Added handling for HttpErrorResponse:

• clear error text
• passing clear response to the dApp
• clear info about which url caused the error

DApp gets this error if used with WalletConnect

{
  "code": 503,
  "message": "HTTP request failed for https://rpc.ghostnet.teztnets.com/chains/main/blocks/head/context/constants (503) Service Unavailable - The server is temporarily unable to handle the request. Please try again later or contact support.",
  "data": [
    503,
    "Service Unavailable - The server is temporarily unable to handle the request. Please try again later or contact support.",
    "",
    "https://rpc.ghostnet.teztnets.com/chains/main/blocks/head/context/constants"
  ]
}

Types of changes

• Bugfix
• New feature
• Refactor
• Breaking change
• UI fix

Steps to reproduce

Screenshots

Add the screenshots of how the app used to look like and how it looks now

Before:

The only useful message comes for error 500. So we need to strip it from tags and keep for the user:

Data-polling:

Now:

Data polling:

Checklist

• Tests that prove my fix is effective or that my feature works have been added
• Documentation has been added (if appropriate)
• Screenshots are added (if any UI changes have been made)
• All TODOs have a corresponding task created (and the link is attached to it)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
umami-embed-iframe	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 15, 2025 4:51pm
umami-embed-iframe-ghostnet	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 15, 2025 4:51pm
umami-v2-web	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 15, 2025 4:51pm
umami-v2-web-storybook	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 15, 2025 4:51pm