Better solution would be to investigate why this happens in backends in
the first place. But they seem to fetch and combine data in different
ways from various sources, which is a bit complicated.

When we try to look up addons later by package name we would
find nothing and crash

BUG:464357
FIXED-IN:5.27

Aleix Pol Gonzalez authored Jan 31, 2023 and Aleix Pol Gonzalez committed Feb 01, 2023

We cannot use roughCount as the value for i18np(). It's a string and we
need a number.

As it's <1000 JS will be overly smart and convert the number into a string
but eventually we give "1000+" and then the conversion returns 0. Without
warnings. 👍

BUG: 464882

Also fetch the metadata for the apps that are available on the repo but
have different branches to choose from.

Since the branches model is not something appstream accounts for, so we
all get confused. Therefore, we don't look for it in the metainfo file from
the app and just add the bundle to it so it fits with the rest of components.

BUG: 464128

It's literally what the method does.

No need to install and uninstall the flatpakref file, we are already proving
it's the same instance as in testInstallApp.

After we have figured out the component, we ought to try again
converting the component into a FlatpakResource since the flatpak id
isn't necessarily the same as the appstream id.

GIT_SILENT

This is needed to make the translations work inside plasma-discover.

GIT_SILENT

Drop assumptions of flatpak id being the same as the appstream id.

BUG: 464206

When host could not be reached, or does not reply for too long, we
should eventually abort and report an error, so that frontend code
could show an error notification and offer a retry button (in case it
does not show it all the time).

First rule of Flickable: manually account for margins.

Combine two chunks of the same straight like into one chunk.
And also reduce indentation to 2 spaces, which is more common for SVG.

GIT_SILENT

GIT_SILENT