Ghost/core/frontend/services/theme-engine/index.js

const active = require('./active');

module.exports = {
    getActive: active.get,
    setActive: active.set,
    loadCoreHelpers: require('./handlebars/helpers').loadCoreHelpers,
    middleware: require('./middleware')
};
Moved activate from themes to the bridge refs: https://github.com/TryGhost/Ghost/commit/bf0823c9a2ddbc93ad0ddcec36eed130c8c5a203 - continuing the work of splitting up the theme service into logical components Theme activations are a trickier piece of the theme split puzzle because they are called from the API and theme service on boot in different ways. Activations require a theme to have been validated at different levels. Validations are also tricky - do they belong to the theme engine, or the theme service? There are then several different flows for activations: - On Boot - API "activate" call - API override on upload or install via setFromZip, which is a method in the storage layer These calls all have quite different logical flows at the moment, and need to be unified For now, I've moved the existing "activate" function onto the bridge. This allows the theme service to be split from the frontend, and refactoring can start from there. I hope to move this so there is less code in the actual bridge very soon, but my goal is not to require any server packages in the frontend part of this I think ideally: - all activation code, including validation, should probably be part of the theme engine - the theme engine should offer 3 methods: getActive() canActivate() and activate() - the theme service is then only responsible for loading themes in and out of storage, JSON responses for the API, and handing themes to the frontend via the bridge at the appropriate moment 2021-04-27 14:49:48 +03:00			`const active = require('./active');`

Moved handlebars utils to new theme engine service refs: https://github.com/TryGhost/Ghost/commit/bf0823c9a2ddbc93ad0ddcec36eed130c8c5a203 - continuing the work of splitting up the theme service into logical components 2021-04-19 17:41:18 +03:00			`module.exports = {`
Moved activate from themes to the bridge refs: https://github.com/TryGhost/Ghost/commit/bf0823c9a2ddbc93ad0ddcec36eed130c8c5a203 - continuing the work of splitting up the theme service into logical components Theme activations are a trickier piece of the theme split puzzle because they are called from the API and theme service on boot in different ways. Activations require a theme to have been validated at different levels. Validations are also tricky - do they belong to the theme engine, or the theme service? There are then several different flows for activations: - On Boot - API "activate" call - API override on upload or install via setFromZip, which is a method in the storage layer These calls all have quite different logical flows at the moment, and need to be unified For now, I've moved the existing "activate" function onto the bridge. This allows the theme service to be split from the frontend, and refactoring can start from there. I hope to move this so there is less code in the actual bridge very soon, but my goal is not to require any server packages in the frontend part of this I think ideally: - all activation code, including validation, should probably be part of the theme engine - the theme engine should offer 3 methods: getActive() canActivate() and activate() - the theme service is then only responsible for loading themes in and out of storage, JSON responses for the API, and handing themes to the frontend via the bridge at the appropriate moment 2021-04-27 14:49:48 +03:00			`getActive: active.get,`
			`setActive: active.set,`
Moved active theme to new theme engine service refs: https://github.com/TryGhost/Ghost/commit/bf0823c9a2ddbc93ad0ddcec36eed130c8c5a203 - continuing the work of splitting up the theme service into logical components - this is where it starts to get fiddly as the getActive function in themeService index is required across the frontend/backend mostly due to its use in the getApiVersion method - for now left one usage of the getActive method in place in ghost-locals middleware ready for the next phase of the refactor, which will move some of the themeService index into a shared location 2021-04-23 15:22:45 +03:00			`loadCoreHelpers: require('./handlebars/helpers').loadCoreHelpers,`
Moved theme middleware to new theme engine service refs: https://github.com/TryGhost/Ghost/commit/bf0823c9a2ddbc93ad0ddcec36eed130c8c5a203 - continuing the work of splitting up the theme service into logical components 2021-04-23 17:16:59 +03:00			`middleware: require('./middleware')`
Moved handlebars utils to new theme engine service refs: https://github.com/TryGhost/Ghost/commit/bf0823c9a2ddbc93ad0ddcec36eed130c8c5a203 - continuing the work of splitting up the theme service into logical components 2021-04-19 17:41:18 +03:00			`};`