Show error screen instead of 404 screen if backend response is 500

[jennydaman]

No description provided.

[TateDeVito]

Hey I'd like to take a look at this! Is there a specific back end response that we want to target?

[jennydaman]

Hello @TateDeVito

There's nothing specific we're trying to target. 500 errors are pretty rare too.

Basically, most of the API requests are unchecked.

ChRIS_store_ui/src/components/Plugin/PluginMeta.jsx

Lines 50 to 52 in fc42f59

	const pluginMeta = await this.fetchPluginMeta(pluginName);
	const versions = await this.fetchPluginVersions(pluginMeta);
	const collaborators = await this.fetchPluginCollaborators(pluginMeta);

So a JavaScript Exception gets thrown and the component fails to load. As a catch-call, the parent Router will show the NotFound component which is a graphic depicting a "404" message. It usually works but can be misleading.

ChRIS_store_ui/src/components/Router/Router.jsx

Line 30 in fc42f59

<Route component={NotFound} />

[janvi01]

Hey @jennydaman I want to take up this issue.

[janvi01]

Hey, thanks for assigning. @jennydaman
Please can you elaborate "error screen"? Does it mean displaying an error message?

[JulianaSau]

Hi, id like to work on this issue