handle errors in redux queries

[tvandort]

Description Of Changes

Adds a middleware that turns redux query failures into toasts. Should we consider pushing to an error page?

Code Changes

• Redux error middleware.

Steps to Confirm

1. list any manual steps for reviewers to confirm the changes

Pre-Merge Checklist

• Issue requirements met
• All CI pipelines succeeded
• CHANGELOG.md updated
  • Add a db-migration This indicates that a change includes a database migration label to the entry if your change includes a DB migration
  • Add a high-risk This issue suggests changes that have a high-probability of breaking existing code label to the entry if your change includes a high-risk change (i.e. potential for performance impact or unexpected regression) that should be flagged
  • Updates unreleased work already in Changelog, no new entry necessary
• Followup issues:
  • Followup issues created
  • No followup issues
• Database migrations:
  • Ensure that your downrev is up to date with the latest revision on main
  • Ensure that your downgrade() migration is correct and works
    • If a downgrade migration is not possible for this change, please call this out in the PR description!
  • No migrations
• Documentation:
  • Documentation complete, PR opened in fidesdocs
  • Documentation issue created in fidesdocs
  • If there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry
  • No documentation updates required

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
fides-plus-nightly	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 28, 2025 4:47pm
fides-privacy-center	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 28, 2025 4:47pm

[jpople]

Looks good-- I would personally favor this approach to an error page, I think it gives more context for what's happening when something goes wrong. Open to other opinions though.

[tvandort]

Looks good-- I would personally favor this approach to an error page, I think it gives more context for what's happening when something goes wrong. Open to other opinions though.

I considered that, I would also prefer a page.

My question is, is it safe for me to do that here?

[cypress]

fides    Run #12882

Run Properties:   Passed #12882  •  e70d952886: handle errors in redux queries (#6094)

Project	fides
Branch Review	main
Run status	Passed #12882
Run duration	00m 55s
Commit	e70d952886: handle errors in redux queries (#6094)
Committer	Tom Van Dort
View all properties for this run ↗︎

---

Test results
Failures	0
Flaky	0
Pending	0
Skipped	0
Passing	5
⚠️ You've recorded test results over your free plan limit. Upgrade your plan to view test results.
View all changes introduced in this branch ↗︎