fix: ignore-invalid-uri-evidences

[kemuru]

PR-Codex overview

The focus of this PR is to update the Node version, handle evidence loading errors, and improve URI fetching in React components.

Detailed summary

• Updated Node version to 16.20.2
• Improved error handling for evidence loading
• Enhanced URI fetching in components for better performance

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[netlify]

✅ Deploy Preview for kleros-court ready!

Name	Link
🔨 Latest commit	f24a31f
🔍 Latest deploy log	https://app.netlify.com/sites/kleros-court/deploys/662fdcc06f36a400088bb80d
😎 Deploy Preview	https://deploy-preview-408--kleros-court.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[gmkung]

@kemuru thanks for pushing the fix.
If I read it correctly, it will now ignore non-URI values, but if an evidence entry is a non-existent URI (e.g. 404 error or other non 200 responses), the evidenceFetcher will still error out and return no evidence at all?

[gmkung]

LGTM now!
@kemuru does the error field get displayed in the UI or does the Court UI ignore it for now?

[alcercu]

lgtm

[kemuru]

LGTM now! @kemuru does the error field get displayed in the UI or does the Court UI ignore it for now?

the UI should display the error card in case there is a valid URI but the network request failed to that URI, if that's your question. it does not display the URI field in that case, as a matter of fact, I could add that.

[sonarcloud]

Quality Gate passed

Issues
21 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud