In the new data model, some field operate as keys for other parts of the model.
This now performs some validations and will throw an error if fields are missing.
For example: a Game must have an Engine, but does not require datafiles
Update the compatibility page to use the new data models.
- Notes are now generated based on game ids, platforms and support level
- We no longer need multiple compatibilty files, only the deltas in one file
- Support level text is now localizable
- Keep support for the old model for versions < 2.0.0
With YAML being a very flexible format, it would be good to have some consistency with how it is formatted. Flathub is a pretty commonly used repository and has good YAML guidelines, so I think it's good to reflect them.
Fixes the following Codacy issues:
* Avoid variables with short names like `$a`. Configured minimum length is 3.
* Avoid unused local variables such as '$key'.
Since it appears that #110 will require compatibility data to be changed from XML to YAML, I wanted to practice and change a simpler page from XML to YAML. If merged, I'm willing to convert other pages as well (e.g. Links, Press Articles, Screenshots, FAQs) as well
Since we can't use the filenames for stripping out the version information,
we have to rely on set values in Constants.php like we do for the Debian
and Tools packages.
Fixes empty version string for the recommended downloads offered
for Android users.
This also changes the behavior that when a user clicks on a news
article, he will get all news articles from the same day. The reasoning
is a) we barely have more than 1 article a day. b) if a user wanted a
hotlink to a particular news article, he might get two different ones
which is odd.