mirror of
https://github.com/esphome/esphome.git
synced 2024-11-22 15:08:10 +01:00
My Home-IoT
2f07225984
* 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. * Make some Action methods protected Apparently play()/stop() etc. are not meant to be called directly by users of the class and if they're called directly that would not give the expected result for the classes that have an empty play(). Make all methods except play_complex, stop_comples and is_running protected. While there also make RemoteTransmitterActionBase::encode protected. * lint * format Co-authored-by: Guillermo Ruffino <glm.net@gmail.com> |
||
|---|---|---|
| .devcontainer | ||
| .github | ||
| docker | ||
| esphome | ||
| script | ||
| tests | ||
| .clang-format | ||
| .clang-tidy | ||
| .coveragerc | ||
| .dockerignore | ||
| .editorconfig | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitpod.yml | ||
| .pre-commit-config.yaml | ||
| .travis.yml | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| MANIFEST.in | ||
| platformio.ini | ||
| pylintrc | ||
| pytest.ini | ||
| README.md | ||
| requirements.txt | ||
| requirements_test.txt | ||
| setup.cfg | ||
| setup.py | ||
ESPHome 
Documentation: https://esphome.io/
For issues, please go to the issue tracker.
For feature requests, please see feature requests.