2015-08-31 16:59:56 +03:00
|
|
|
// # Client API
|
|
|
|
// RESTful API for the Client resource
|
2018-07-23 15:38:40 +03:00
|
|
|
const Promise = require('bluebird'),
|
|
|
|
{extend, omit} = require('lodash'),
|
2017-12-14 00:20:02 +03:00
|
|
|
pipeline = require('../lib/promise/pipeline'),
|
2017-12-14 00:14:19 +03:00
|
|
|
localUtils = require('./utils'),
|
2017-09-12 18:31:14 +03:00
|
|
|
models = require('../models'),
|
2017-12-12 00:47:46 +03:00
|
|
|
common = require('../lib/common'),
|
2018-07-23 15:38:40 +03:00
|
|
|
docName = 'clients';
|
|
|
|
|
|
|
|
let clients;
|
2015-08-31 16:59:56 +03:00
|
|
|
|
|
|
|
/**
|
|
|
|
* ### Clients API Methods
|
|
|
|
*
|
2017-12-11 22:27:09 +03:00
|
|
|
* **See:** [API Methods](events.js.html#api%20methods)
|
2015-08-31 16:59:56 +03:00
|
|
|
*/
|
|
|
|
clients = {
|
|
|
|
|
|
|
|
/**
|
|
|
|
* ## Read
|
|
|
|
* @param {{id}} options
|
|
|
|
* @return {Promise<Client>} Client
|
|
|
|
*/
|
|
|
|
read: function read(options) {
|
2018-07-23 15:38:40 +03:00
|
|
|
const attrs = ['id', 'slug'];
|
|
|
|
let tasks;
|
2015-08-31 16:59:56 +03:00
|
|
|
|
|
|
|
/**
|
|
|
|
* ### Model Query
|
|
|
|
* Make the call to the Model layer
|
|
|
|
* @param {Object} options
|
|
|
|
* @returns {Object} options
|
|
|
|
*/
|
|
|
|
function doQuery(options) {
|
|
|
|
// only User Agent (type = `ua`) clients are available at the moment.
|
2018-07-23 15:38:40 +03:00
|
|
|
options.data = extend(options.data, {type: 'ua'});
|
2017-09-27 11:31:41 +03:00
|
|
|
|
2018-07-23 15:38:40 +03:00
|
|
|
return models.Client.findOne(options.data, omit(options, ['data']))
|
2017-09-27 11:31:41 +03:00
|
|
|
.then(function onModelResponse(model) {
|
|
|
|
if (!model) {
|
2017-12-12 00:47:46 +03:00
|
|
|
return Promise.reject(new common.errors.NotFoundError({
|
|
|
|
message: common.i18n.t('common.api.clients.clientNotFound')
|
2017-09-27 11:31:41 +03:00
|
|
|
}));
|
|
|
|
}
|
|
|
|
|
|
|
|
return {
|
|
|
|
clients: [model.toJSON(options)]
|
|
|
|
};
|
|
|
|
});
|
2015-08-31 16:59:56 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
// Push all of our tasks into a `tasks` array in the correct order
|
|
|
|
tasks = [
|
2017-12-14 00:14:19 +03:00
|
|
|
localUtils.validate(docName, {attrs: attrs}),
|
Sorted out the mixed usages of `include` and `withRelated` (#9425)
no issue
- this commit cleans up the usages of `include` and `withRelated`.
### API layer (`include`)
- as request parameter e.g. `?include=roles,tags`
- as theme API parameter e.g. `{{get .... include="author"}}`
- as internal API access e.g. `api.posts.browse({include: 'author,tags'})`
- the `include` notation is more readable than `withRelated`
- and it allows us to use a different easier format (comma separated list)
- the API utility transforms these more readable properties into model style (or into Ghost style)
### Model access (`withRelated`)
- e.g. `models.Post.findPage({withRelated: ['tags']})`
- driven by bookshelf
---
Commits explained.
* Reorder the usage of `convertOptions`
- 1. validation
- 2. options convertion
- 3. permissions
- the reason is simple, the permission layer access the model layer
- we have to prepare the options before talking to the model layer
- added `convertOptions` where it was missed (not required, but for consistency reasons)
* Use `withRelated` when accessing the model layer and use `include` when accessing the API layer
* Change `convertOptions` API utiliy
- API Usage
- ghost.api(..., {include: 'tags,authors'})
- `include` should only be used when calling the API (either via request or via manual usage)
- `include` is only for readability and easier format
- Ghost (Model Layer Usage)
- models.Post.findOne(..., {withRelated: ['tags', 'authors']})
- should only use `withRelated`
- model layer cannot read 'tags,authors`
- model layer has no idea what `include` means, speaks a different language
- `withRelated` is bookshelf
- internal usage
* include-count plugin: use `withRelated` instead of `include`
- imagine you outsource this plugin to git and publish it to npm
- `include` is an unknown option in bookshelf
* Updated `permittedOptions` in base model
- `include` is no longer a known option
* Remove all occurances of `include` in the model layer
* Extend `filterOptions` base function
- this function should be called as first action
- we clone the unfiltered options
- check if you are using `include` (this is a protection which could help us in the beginning)
- check for permitted and (later on default `withRelated`) options
- the usage is coming in next commit
* Ensure we call `filterOptions` as first action
- use `ghostBookshelf.Model.filterOptions` as first action
- consistent naming pattern for incoming options: `unfilteredOptions`
- re-added allowed options for `toJSON`
- one unsolved architecture problem:
- if you override a function e.g. `edit`
- then you should call `filterOptions` as first action
- the base implementation of e.g. `edit` will call it again
- future improvement
* Removed `findOne` from Invite model
- no longer needed, the base implementation is the same
2018-02-15 12:53:53 +03:00
|
|
|
localUtils.convertOptions(),
|
2015-08-31 16:59:56 +03:00
|
|
|
// TODO: add permissions
|
|
|
|
// utils.handlePublicPermissions(docName, 'read'),
|
|
|
|
doQuery
|
|
|
|
];
|
|
|
|
|
|
|
|
// Pipeline calls each task passing the result of one to be the arguments for the next
|
2017-09-27 11:31:41 +03:00
|
|
|
return pipeline(tasks, options);
|
2015-08-31 16:59:56 +03:00
|
|
|
}
|
|
|
|
};
|
|
|
|
|
|
|
|
module.exports = clients;
|