Ghost/core
kirrg001 1e2beface1 Refactored the API layer: do not handle API response after pipelining
no issue

- this has a big underlying problem
- each task in the pipeline can modify the options
- e.g. add a proper permission context
- if we chain after the pipeline, we don't have access to the modified options object
- and then we pass the wrong options into the `toJSON` function of a model
- the toJSON function decides what to return based on options
- this is the easiest solution for now, but i am going to write a spec if we can solve this problem differently
2017-09-28 10:18:18 +01:00
..
client@90706d0b38 Updated Ghost-Admin to 1.9.1 2017-09-26 14:49:00 +01:00
server Refactored the API layer: do not handle API response after pipelining 2017-09-28 10:18:18 +01:00
test 🐛 Fixed missing cache invalidation header when uploading redirects (#9071) 2017-09-27 18:58:33 +01:00
index.js Misc grunt /dev updates 2015-05-28 20:25:14 +01:00