kirrg001 89e4201b67 Clarify the behaviour of defaultColumnsToFetch in the post model ... no issue - add a big comment - describe: - how this works - why this is in place - what does currently not work - and why it will work with channels - @TODO: - figure out how to disallow: - `models.Post.findAll({columns: id})` - `post.save(data)` - this will trigger bookshelf events and model events - url generation currently needs a set of attributes (e.g. slug, published_at) - will be auto-fixed with channels, because you can call `urlService.getUrl(post.id)` - but what doesn't get solved is our model events - e.g. `emitChange` needs `post.get('page')` to determine if it's a page		2018-04-06 13:32:10 +02:00
..
client@7fa52be861	Updated Ghost-Admin: API request without updated_by/created_by	2018-04-05 18:51:58 +02:00
server	Clarify the behaviour of defaultColumnsToFetch in the post model	2018-04-06 13:32:10 +02:00
test	Added tests for event behaviour: updating resources with or without updating it's relations	2018-04-05 18:51:58 +02:00
index.js	Misc grunt /dev updates	2015-05-28 20:25:14 +01:00