In any view that displays information about a title (movie, tv show), the Title ID can be derived from the picture URLs, catalog hrefs and other such URLs - but it would be very handy to also include that ID as its own field.
The title ID is always included in the title link in these cases. Note that title IDs are always the fully qualified URL- not the numeric portion therein. For example, a series and its first season share the same number fragment and and only the rest of the URL distinguishes the two.
Though a primary key may be made up of two ids, that part is fine. But if you decide to change your URLs for any reason, all children apps will break. There needs to be some way to get the primary keys from the api rather than full URLs that we are forced to parse. It would be better to add ID fields.
In any view that displays information about a title (movie, tv show), the Title ID can be derived from the picture URLs, catalog hrefs and other such URLs - but it would be very handy to also include that ID as its own field.
Message edited by Morgon 3 years ago
Michael Hart – 3 years ago
The title ID is always included in the title link in these cases. Note that title IDs are always the fully qualified URL- not the numeric portion therein. For example, a series and its first season share the same number fragment and and only the rest of the URL distinguishes the two.
jonbcampos – 3 years ago
Though a primary key may be made up of two ids, that part is fine. But if you decide to change your URLs for any reason, all children apps will break. There needs to be some way to get the primary keys from the api rather than full URLs that we are forced to parse. It would be better to add ID fields.
Michael Hart – 3 years ago
In a REST API, everything is a resource and is referenced by URL. Why do you feel you need the numeric portion of a title URL?