Closed oahner closed 7 years ago
ah. good catch, thanks.
should be fixed in 0.1.12-SNAPSHOT
. let me know if it works for you.
when would you start-without
/ stop-except
ALL?
It works!
I stumbled upon that behavior on a project that had two states where one (the webserver) doesn't need to be restarted on reset and I had temporarily commented out the other. End result: the webserver state was suddenly getting restarted on reset.
ah.. makes sense. thanks for bringing it up
So, as one would expect,
start-without
andstop-except
, when called with all states available in the system, callstart
/stop
with an empty list, which is normally a noop.Unfortunately the actual call is made with
apply
, which converts the empty list to a seq, which converts the empty seq to nil, which is whatstart
andstop
receive asstates
(as if they were called with no arguments) and start/stop every state in the system.