Timeline for How to maintain consistency when retrieving partial vs. full data in an API Resource
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 9 at 17:36 | comment | added | jmathew | OData also has the same concept. | |
| Aug 9 at 17:23 | comment | added | jmathew |
This is the approach I'd take. Popcorn is what I use for ASP.net APIs to solve this. The client makes queries and provides an include parameter to dictate which fields on each entity is included. Eg: GET http://myservice.com/api/logistics?include=[thing1, thing2, relatedobject[ id, thing1, thing2]]. GraphQL does this by default as well, but that'd be moving away from REST.
|
|
| Aug 9 at 9:56 | history | answered | James | CC BY-SA 4.0 |