luciano/mount
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge branch 'master' into 0.1.11

Browse source
This commit is contained in:
anatoly 2016-11-01 21:24:30 -04:00
commit e9ba02b5a5
3 changed files with 33 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
README.md
View file

@ -299,7 +299,7 @@ All of the above is much easier to understand by looking at examples:
This would start off from 5 states, even though the whole application may have many more states available. It would then exclude two states (i.e. `#'foo/c` and `#'bar/d`), then it will pass runtime arguments `{:a 42}`, and finally it will start the remaining three states: `#'foo/a`, `#'foo/b`, `#'baz/e`.
You may notice that `only` takes a set, while `except` takes a vector in this example. This is done intentionally to demonstraate that both these functions can take any collection of states. `set` would make more sense for most cases though.
You may notice that `only` takes a set, while `except` takes a vector in this example. This is done intentionally to demonstrate that both these functions can take any collection of states. `set` would make more sense for most cases though.
Here is a more "involved" example:
@ -356,7 +356,7 @@ During testing it is often very useful to mock/stub certain states. For example
### Swapping States with Values
The `start-with` function takes values as substitues.
The `start-with` function takes values as substitutes.
Say we have a `send-sms` state:
@ -381,7 +381,7 @@ When running tests it would be great _not_ to send the real text messages, but r
### Swapping States with States
The `start-with-states` function takes other states as substitues:
The `start-with-states` function takes other states as substitutes:
```clojure
(mount/start-with-states {#'app.neo/db #'app.test/test-db
@ -459,9 +459,9 @@ Providing a `:stop` function _is_ optional, but in case a state needs to be clea
### :on-reload
By default a state will be restarted on its redefenition or a namespace recompilation. However it is not always a desired behavior. Sometimes it's ok to have stale references during REPL sessions / development, other times all that is needed is not a "restart", but just a "stop".
By default a state will be restarted on its redefinition or a namespace recompilation. However it is not always a desired behavior. Sometimes it's ok to have stale references during REPL sessions / development, other times all that is needed is not a "restart", but just a "stop".
This behavior could be conrolled with an optional `:on-reload` meta attribute when defining a state.
This behavior could be controlled with an optional `:on-reload` meta attribute when defining a state.
In case _nothing_ needs to be done to a running state on reload / recompile / redef, set `:on-reload` to `:noop`:

BIN
doc/img/mount-logo.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 99 KiB

19
src/mount/core.cljc
View file

@ -301,6 +301,25 @@
(var-to-str to) :state))
states))
;; restart on events
(defprotocol ChangeListener
(add-watcher [this ks watcher])
(on-change [this k]))
(deftype RestartListener [watchers]
ChangeListener
(add-watcher [_ ks state]
(doseq [k ks]
(swap! watchers update k #(conj % state))))
(on-change [_ k]
(let [states (@watchers k)]
(apply stop states)
(apply start states))))
;; explicit, not composable (subject to depreciate?)
(defn stop-except [& states]