Ghost/core/test/unit/controllers/frontend
Katharina Irrgang 0201c431d7 🔥 do not store settings in config (#7924)
* 🎨  🔥  do not store settings in config and make settings cache easier available

- remove remembering settings value in theme config
- if we need a cache value, we are asking the settings cache directly
- instead of settings.getSettingSync we use settings.cache.get

- added TODO:
  - think about moving the settings cache out of api/settings
  - we could create a folder named cache cache/settings
  - this settings cache listens on model changes for settings
  - decoupling

* 🔥  remove timezone from config

- no need to store in overrides config and in defaults settings

* 🎨  context object helper

- replace config.get('theme') by settings cache

* 🎨  replace config.get('theme') by settings.cache.get

* 🎨  adapt tests

* fixes from comments
2017-02-03 13:15:11 +00:00
..
channel-config_spec.js improvement: jshint/jscs 2016-06-17 22:59:47 +02:00
channels_spec.js 🚨 change logic for test/utils/configUtils 2016-09-20 15:59:34 +01:00
context_spec.js [FEATURE] AMP (#7229) 2016-08-22 18:49:27 +02:00
error_spec.js Error creation (#7477) 2016-10-06 13:27:35 +01:00
fetch-data_spec.js 🔥 do not store settings in config (#7924) 2017-02-03 13:15:11 +00:00
format-response_spec.js improvement: jshint/jscs 2016-06-17 22:59:47 +02:00
index_spec.js 🔥 do not store settings in config (#7924) 2017-02-03 13:15:11 +00:00
post-lookup_spec.js 🔥 do not store settings in config (#7924) 2017-02-03 13:15:11 +00:00
render-channel_spec.js Move internal tags out of labs (#7519) 2016-10-10 09:51:03 +01:00
templates_spec.js improvement: jshint/jscs 2016-06-17 22:59:47 +02:00