How to organize API routes?
There is a .NET 6 WebApi with 2 controllers:
PlatformsController and OrdersController.
Now, in order to get orders, passing platformId is mandatory.
/orders/{platformId}
But ideally the api route would look like:
/platforms/{platformId}/orders/{orderId}.
But since orders must belong to platforms I'm forced to use 1 controller - PlatformsController.
But in this case everything will have to be inside PlatformsController and swagger will show only one controller and won't be separated by orders for example. How to get around this?
PlatformsController and OrdersController.
Now, in order to get orders, passing platformId is mandatory.
/orders/{platformId}
But ideally the api route would look like:
/platforms/{platformId}/orders/{orderId}.
But since orders must belong to platforms I'm forced to use 1 controller - PlatformsController.
But in this case everything will have to be inside PlatformsController and swagger will show only one controller and won't be separated by orders for example. How to get around this?
