Files
esphome-lsm6ds/esphome/core
Andrew Zaborowski da390d32f8 Move stop/is_running implementation to Action base class
Try to fix issue #1105.  Until now if an UpdateComponentAction, a
LambdaAction, or any action that can contain those inside their
"else" or "then" action lists, resulted in a call to script.stop on
the script that contains them, the script would continue running,
because they didn't implement a stop() method.  Basically only
the asynchronous ones did: DelayAction, WaitUntilAction and
ScriptWaitAction.

With this change num_running_ in Action replaces
DelayAction::num_running_ and WaitUntilAction::triggered_ to provide
the same is_running logic to other actions.
2020-05-01 12:44:30 +02:00
..
2019-12-07 18:53:20 +01:00
2019-06-09 17:03:51 +02:00
2019-12-04 19:30:10 +01:00
2019-12-04 19:30:10 +01:00
2019-07-03 16:34:40 +02:00
2019-10-31 20:25:16 +01:00
2019-10-18 14:46:44 +02:00
2019-10-18 14:46:44 +02:00
2019-06-03 16:07:15 +02:00