Ghost/test/regression/api/canary/content
Nazar Gargol d6267340a1 Updated Content API resource ordering to be same as slugs in filter
closes #11994

- Adds support for ordering based on slug filter  that contains a slug-is-in filter. It is applied only to Content API's resources - post, page, tag, author. The order is applied in the same order in which slugs appear in the filter.
- For, example providing following  query parameter filter for any of the above resources: `?filter=slug:[kitchen-sink,bacon,chorizo]`, would filter them by these slugs and order in the same way defined in the filter
- Can be used in handlebars templates in following way: `{{#get "tags" filter="slug:[slugs,of,the,tags,in,order]"}}`
- The property conteining this new order is assigned to `autoOrder` instead of `rawOrder` intentionally. This explicit asstignment would allow distinguishing where the 'orderRaw' comes from the model or the API layer. Apart from  adding necessary context this separation makes it easier to refactor separately model layer and API specific ordering in the future
- This commit also fixes default filtering for `author` resource in Content API. The serializer was never used before as it was missing from `serializers/index.js` module.
2020-07-10 18:33:00 +12:00
..
authors_spec.js Updated Content API resource ordering to be same as slugs in filter 2020-07-10 18:33:00 +12:00
pages_spec.js Updated Content API resource ordering to be same as slugs in filter 2020-07-10 18:33:00 +12:00
posts_spec.js Updated Content API resource ordering to be same as slugs in filter 2020-07-10 18:33:00 +12:00
tags_spec.js Updated Content API resource ordering to be same as slugs in filter 2020-07-10 18:33:00 +12:00
utils.js 🐛 Updated access to be true by default in v3 API 2020-07-06 16:04:29 +01:00