Timeline for answer to Is it legal for a RESTful API to provide different structures for a given resource? How should that be modeled? by Cormac Mulhall
Current License: CC BY-SA 3.0
Post Revisions
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 13, 2017 at 13:03 | comment | added | D.Shawley | @RodrigoLira - I think that you've identified a key point in your comment. Do not conflate a clean swagger spec with a well designed API. | |
| Jan 12, 2017 at 14:11 | comment | added | Rodrigo Lira | You're right. Different resources. @Gaurav what you wrote is exactly how i'm going. I was hanging too much on the fact that my swagger specification would have two very close definitions but I guess that's ok. | |
| Jan 12, 2017 at 14:09 | vote | accept | Rodrigo Lira | ||
| Jan 11, 2017 at 18:40 | comment | added | Gaurav |
You can calibrate this to precisely meet your needs: /stores could include one thumbnail picture, and then /stores/{storesId} or /stores/{storeId}/pictures could provide every available picture, with that link included in your first response.
|
|
| Jan 11, 2017 at 18:00 | history | answered | Cormac Mulhall | CC BY-SA 3.0 |