Open dustinvtran opened 2 years ago
Thoughts: it's difficult to link igdb link to entry because the link doesn't contain the ID.
How's it currently linked? a backend id?
Our API provides the URLs. They're not derived from the entry ID.
commonMetadata: {
apiRefs: { name: string, ref: string }[]
externalUrls: { name: string, url: string }[]
}
example igdb link: https://www.igdb.com/games/pokemon-ruby
Since links cannot be linked to DB entries reliably I think it's better to delete an entry and re-do the search when you want to change which DB entry you're basing it off of
That SGTM on the backend implementation. Hopefully UI-wise, the user won't notice a difference.
Given the workaround, will label this as P2 as it's only a minor inconvenience for users.
An alternative would be to provide the option to re-do the search on an existing entry, but for now let's say you just have to delete the entry.
We should keep all the database fields read-only but allow users to edit the database link that the entry is connected to.
Example. You write a custom entry for an indie movie that hasn't yet appeared on TMDB. It appears later. Therefore you want to link your existing entry to TMDB. Moreover, you can now remove your manual information like "year", "director", etc. in order to reduce maintenance.
Example. You add an entry for a video game but the entry only exists in IGDB and not HLTB. The entry appears on HLTB. Therefore you want to link your existing entry to HLTB.