Move registration of postUpdateHooks to the corresponding source files

This completely decouples settings.coffee from all other background
source files, so that it can (eventually) also be used in the frontend.

1 files changed, 3 insertions, 10 deletions

diff --git a/background_scripts/settings.coffee b/background_scripts/settings.coffee
index 44676ad7..6b33d239 100644
--- a/background_scripts/settings.coffee
+++ b/background_scripts/settings.coffee
@@ -75,17 +75,10 @@ root.Settings = Settings =
 
   has: (key) -> key of localStorage
 
-  # For settings which require action when their value changes, add hooks here called from
-  # options/options.coffee (when the options page is saved), and from background_scripts/sync.coffee (when an
+  # For settings which require action when their value changes, add hooks to this object, to be called from
+  # options/options.coffee (when the options page is saved), and by Settings.storeAndPropagate (when an
   # update propagates from chrome.storage.sync).
-  postUpdateHooks:
-    keyMappings: (value) ->
-      root.Commands.clearKeyMappingsAndSetDefaults()
-      root.Commands.parseCustomKeyMappings value
-      root.refreshCompletionKeysAfterMappingSave()
-
-    exclusionRules: (value) ->
-      root.Exclusions.postUpdateHook value
+  postUpdateHooks: {}
 
   # postUpdateHooks convenience wrapper
   performPostUpdateHook: (key, value) ->