Error propagation from backend to frontend
How do we handle error propagation?
Example 1:
Currently when I call http://localhost:3000/config/simulation-4 (a configuration that doesn't exist) there is an error in the backend but the frontend just shows the loading dots.
- What has to be returned so that the frontend can show an error?
- What will we displayed? A message? A generic 404 page?
Example 2:
The configuration file is wrong. The backend will detect this and throws an error. This should be only relevant in development mode for each app. But it would be a nice development experience if the frontend displays the configuration error and the backend stays responsive instead of breaking down.