ghost/core/server/themes/index.js

var themeLoader = require('./loader');

// @TODO: reduce the amount of things we expose to the outside world
// Make this a nice clean sensible API we can all understand!
module.exports = {
    init: themeLoader.init,
    loadAll: themeLoader.loadAllThemes,
    loadOne: themeLoader.loadOneTheme,
    list: require('./list'),
    validate: require('./validate')
};
Theme loading part 1 (#7989) no issue * ✨ Add new server start & stop events * 🔥 Get rid of unused availableApps concept - when we need an API endpoint for a list of apps, we'll build one 😝 * ✨ Move theme loading into a module - move loading from API method to a module method and use as needed - wire up read one vs read all as per LTS - read one (the active theme) on boot, and read the rest after - fudge validation - this isn't all that helpful * Settings API tests need to preload themes - this used to automatically happen as part of loading settings - now we need to trigger this to happen specifically for this test 2017-02-21 23:26:19 +00:00			`var themeLoader = require('./loader');`

🔥✨ No more availableThemes (#8085) no issue 🎨 Switch themes API to use config.availableThemes - this gets rid of the only places where settings.availableThemes are used 🔥 Get rid of settings.availableThemes - this is no longer used anywhere - also get rid of every related call to updateSettingsCache 🔥 Replace config.availableThemes with theme cache - Creates a tailor-made in-memory cache for themes inside the theme module - Add methods for getting & setting items on the cache - Move all references to config.availableThemes to use the new cache - This can be abstracted later to support other kinds of caches? 🎨 Start improving theme lib's API Still TODO: simplifying/clarifying: - what is the structure of the internal list - what is the difference between a package list, and a theme list? - what is the difference between reading a theme and loading it? - how do we update the theme list (add/remove) - how do we refresh the theme list? (hot reload?!) - how do we get from an internal list, to one that is sent as part of the API? - how are we going to handle theme storage: read/write, such that the path is configurable 🎨 Use themeList consistently 🎨 Update list after storage 2017-03-02 16:53:48 +00:00			`// @TODO: reduce the amount of things we expose to the outside world`
			`// Make this a nice clean sensible API we can all understand!`
Theme loading part 1 (#7989) no issue * ✨ Add new server start & stop events * 🔥 Get rid of unused availableApps concept - when we need an API endpoint for a list of apps, we'll build one 😝 * ✨ Move theme loading into a module - move loading from API method to a module method and use as needed - wire up read one vs read all as per LTS - read one (the active theme) on boot, and read the rest after - fudge validation - this isn't all that helpful * Settings API tests need to preload themes - this used to automatically happen as part of loading settings - now we need to trigger this to happen specifically for this test 2017-02-21 23:26:19 +00:00			`module.exports = {`
			`init: themeLoader.init,`
🔥✨ No more availableThemes (#8085) no issue 🎨 Switch themes API to use config.availableThemes - this gets rid of the only places where settings.availableThemes are used 🔥 Get rid of settings.availableThemes - this is no longer used anywhere - also get rid of every related call to updateSettingsCache 🔥 Replace config.availableThemes with theme cache - Creates a tailor-made in-memory cache for themes inside the theme module - Add methods for getting & setting items on the cache - Move all references to config.availableThemes to use the new cache - This can be abstracted later to support other kinds of caches? 🎨 Start improving theme lib's API Still TODO: simplifying/clarifying: - what is the structure of the internal list - what is the difference between a package list, and a theme list? - what is the difference between reading a theme and loading it? - how do we update the theme list (add/remove) - how do we refresh the theme list? (hot reload?!) - how do we get from an internal list, to one that is sent as part of the API? - how are we going to handle theme storage: read/write, such that the path is configurable 🎨 Use themeList consistently 🎨 Update list after storage 2017-03-02 16:53:48 +00:00			`loadAll: themeLoader.loadAllThemes,`
			`loadOne: themeLoader.loadOneTheme,`
			`list: require('./list'),`
🔥 🎨 Themes & settings misc cleanup (#8061) no issue 🔥 remove unused loadThemes API method 🚨 Add tests for themes.readOne 🔥 Don't update settings cache for imports - this isn't needed as of #8057 - settings.edit fires an event, that will result in the update happening automatically 🎨 Move validation to themes - slowly collecting all theme-related code together 🔥 Reduce DEBUG output - all this info is a bit tooooo much! 2017-02-27 22:30:49 +00:00			`validate: require('./validate')`
Theme loading part 1 (#7989) no issue * ✨ Add new server start & stop events * 🔥 Get rid of unused availableApps concept - when we need an API endpoint for a list of apps, we'll build one 😝 * ✨ Move theme loading into a module - move loading from API method to a module method and use as needed - wire up read one vs read all as per LTS - read one (the active theme) on boot, and read the rest after - fudge validation - this isn't all that helpful * Settings API tests need to preload themes - this used to automatically happen as part of loading settings - now we need to trigger this to happen specifically for this test 2017-02-21 23:26:19 +00:00			`};`