Lets say, I have a scenario where I have to expose an api to fetch supported shirt sizes(
My initial thought was
/v1/shirts/sizes - But this clashes with the existing fetch shirt by id api.
My friend is suggesting, we can have resource named metadata, which can be used to list all static information throughout our application. Something like
But I am not happy with having
metadata api since it have completely unrelated sub-resources(shirtsizes , supported-lanugages)
How to handle this scenario? Is there any way to achieve it?