This PR almost entirely eliminates the concept of URL "components" from the codebase.
Poketo object IDs are made of three components joined by a colon (eg. meraki-scans:senryu-girl:5). Previously, there was a bunch of functions to convert between components and object IDs in order to support a URL structure like this: /read/meraki-scans/senryu-girl/5. I think I finally clued in to how silly it was to contort IDs to fit that purpose.
These changes update the URL structure to simply use the IDs: /read/meraki-scans:senryu-girl:5. After all, colons are valid URL characters.
With this change, we can remove a bunch of random Flow types used to distinguish the URL components too.
This PR almost entirely eliminates the concept of URL "components" from the codebase.
Poketo object IDs are made of three components joined by a colon (eg.
meraki-scans:senryu-girl:5). Previously, there was a bunch of functions to convert between components and object IDs in order to support a URL structure like this:/read/meraki-scans/senryu-girl/5. I think I finally clued in to how silly it was to contort IDs to fit that purpose.These changes update the URL structure to simply use the IDs:
/read/meraki-scans:senryu-girl:5. After all, colons are valid URL characters.With this change, we can remove a bunch of random Flow types used to distinguish the URL components too.