jeans/home-assistant.io
jeans/home-assistant.io
1
0
Fork 0
mirror of https://github.com/home-assistant/home-assistant.io.git synced 2025-07-28 03:37:06 +00:00
Code Issues Packages Projects Releases Wiki Activity

Script variable scopes (#37720)

Browse Source
This commit is contained in:
Artur Pragacz 2025-02-26 16:23:11 +01:00 committed by GitHub
parent b97fcffdab
commit 0ad1274bf8
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
source/_docs/scripts.markdown
View File

@ -94,7 +94,7 @@ Variables can be templated.
### Scope of variables
Variables have local scope. This means that if a variable is changed in a nested sequence block, that change will not be visible in an outer sequence block.
Variables defined by the `variables` {% term action %} have local scope. This means that if a variable is changed in a nested sequence block, that change will not be visible in an outer sequence block.
Inside the `if` sequence the `variables` {% term action %} will only alter the `people` variable for that sequence.
@ -858,6 +858,8 @@ Some of the caveats of running {% term actions %} in parallel:
they too have finished or errored.
- Variables created/modified in one parallelized {% term action %} are not available
in another parallelized {% term action %}. Each step in a parallelized has its own scope.
- The response data of a parallelized {% term action %} is however also available outside of its
own scope. This is especially useful for parallelizing execution of long-running {% term actions %}.
## Stopping a script sequence