Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make expensive metadata requestable with "include" key #5

Open
qwesda opened this issue Aug 20, 2014 · 0 comments
Open

make expensive metadata requestable with "include" key #5

qwesda opened this issue Aug 20, 2014 · 0 comments
Labels

Comments

@qwesda
Copy link

qwesda commented Aug 20, 2014

depends on #2

the metadata key in the api response should by default only contain information, that is available without any additional queries/processing.

expensive metadata should be provided if requested.

{
  "columns": [ ... ],
  "limit": 10,
  "order_by": [ ["total", "DESC"] ],
  "where": [],
  "offset_id": 8346,
  "offset": 0,
  "include" : [ 
    "count", // number of items
    "omitted", // number of items omitted due to order parameters (implicit NOT NULL)
    "prev", // url with offset_id for preceding chunk
  ]
}
@qwesda qwesda added the feature label Aug 21, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant