File->"Playable" should be true by default/if the value is absent

No description provided.

can we assume every entry in the database has at least one gb/gbc/gba playable file?

can we assume every entry in the database has at least one gb/gbc/gba playable file?

nope not really, there are some metadata-only entries. I'm not sure what this issue was about lol

I'm not sure what this issue was about lol

I remember an issue like that some time ago too.

Anyway, this leads in some complications:

we cannot assume that every entry in the database has at least one playable file
we cannot assume that the first file in the "files" array is the most up-to-date version (we may have contributors that has put most recent entry file at the end and not beginning)

Therefore, i'd edit this issue with "add a playable field to AT LEAST one playable file, if not present".

The work should be something like:

scan every json
if "playable: true" is present and the file is a gb/gbc/gba whatever playable file, good
if not, then add it to the first occurrence

We still have the second problem (not most up-to-date guaranteed), but at least we have the guarantee that each file is listed and playable.

I don't remember if this check already occurs at a certain point in the pipeline...

Navigation Menu