Home page doesn't load (new elements lead to exception)

[sifferhans]

The home page doesn't load.

[SimonSimCity]

Seems to be fixed without giving it any attention ... Maybe the PR #269 did something, but otherwise I don't know ... @kkuepper do you know about anything that was changed to get this working again?

[kkuepper]

I didn't notice there was an issue about it.

I disabled the project-box for the website.
(Detailed explanation: I added a MinVersion to the project-box element. Since the Website doesn't send an app version, the website doesn't get the project-box in the discover request anymore.)

That does highlight 2 problems though:

1. If a new unknown element is added, the website should just ignore it and not throw an error that prevents the whole list from being shown.
2. I don't know how to update bmm-fetch so that the website knows about the new element. Actually it's only @SimonSimCity that knows how to do that. The best would be to have a github action that creates a new package version automatically.

We must fix at least 1 of those problems.

[SimonSimCity]

IMO, solving 2) would just shorten the time of an error like this to be fixed, whereby 1) would prevent it in the first run from happening. This said, 1) should have the focus here.

Issue 1) should be fixed by #33, and 2) there's not anything more to it than running the 3 commands described in the readme of the package (https://github.com/bcc-code/bmm-sdk).

But this always also depends on how strong the structure of the backend is changed. If there's something which has been replaced, this might eventually pose some issues - same as if data is not according to the specs - the swagger file.

At least the rest of the website remained usable 🤪 Might be good to show something else than a blank page in case of an exception, but that's again part of #33.

Closing this issue as resolved. That an issue like this should not come up again has to be set in #33.