f8b498d6e7
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 |
||
|---|---|---|
| .. | ||
| api | ||
| validation | ||
| brute.js | ||
| cache-control.js | ||
| custom-redirects.js | ||
| error-handler.js | ||
| ghost-locals.js | ||
| labs.js | ||
| log-request.js | ||
| maintenance.js | ||
| pretty-urls.js | ||
| redirect-to-setup.js | ||
| serve-favicon.js | ||
| serve-shared-file.js | ||
| static-theme.js | ||
| theme-handler.js | ||
| uncapitalise.js | ||
| url-redirects.js | ||