Skip to main content

📐 Actions Scope

Some DI actions support special extensions to change where they input files from.

note

When an action modifies files, only the input files, which contain the information to make the changes, change their scope. The target files, those that receive the modifications, maintain their normal external scope. This allows combining two different scopes in the same action, simplifying the work.

External scope​

By default, an external scope is used solely for actions needing input files or folders.

import_bin "/sdcard/my_binary"   # From device storage

update_file "/sdcard/example.txt" "/system/build.prop"  # Both from device storage

Addon Scope​

Use input files from META-INF/addons inside the ZIP.

import_bin_addon "my_binary"   # From META-INF/addons/my_binary

# Only the input file changes scope: META-INF/addons/myfile.txt
# The target file maintains its external scope: /system/build.prop
update_file_addon "myfile.txt" "/system/build.prop"

Zip Scope​

Use files directly from the ZIP, including folder paths.

import_bin_zip "my_binary"   # From the installation ZIP root

# Only the input file changes scope: folder/myfile.txt (internal path of the installation ZIP)
# The target file maintains its external scope: /system/build.prop
update_file_zip "folder/example.txt" "/system/build.prop"