Initial error handling implementation

[roll]

• fixes Better error handling on the client #295

---

In this PR we start catching all the possible server errors and reflect them in the UI (exact UI can be updated later). Currently, error handling in actions is quite verbose but can be improved in #430 (using some kind of error boundaries in actions). Also, this iteration doesn't fully cover nested action errors (still can get into an inconsistent state), which also needs to be addressed in #430.

Other follow-up issues:

• Identify possible errors (mostly server) and review/update error messages #432
• Implement proper loading states #433

[cloudflare-workers-and-pages]

Deploying opendataeditor with    Cloudflare Pages

Latest commit:	2bdd46e
Status:	✅  Deploy successful!
Preview URL:	https://0f633640.opendataeditor.pages.dev
Branch Preview URL:	https://295-error-handling.opendataeditor.pages.dev

View logs

[pdelboca]

Looks good @roll ! It reminds me a lot to go pattern:

result, err := doSomething()
if err != nil {
    log.Fatal(err)
}

Note: Is is truly necessary to repeat all the Error.tsx components?

[roll]

@pdelboca
Thanks!

Looks good @roll ! It reminds me a lot to go pattern:

Yea, exactly. Still not sure if it's the best one as it's great without nesting but if you have nested actions (e.g. doSomethign -> loadFields -> client.load) you need to have signature on the actions as well. I'll investigate further

Note: Is is truly necessary to repeat all the Error.tsx components?

I think it will be eliminated in #430; it will have an error state only in one store so the error component will be global as well