Scott.Idem/OSIT-AE-App-Svelte
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor(launcher): prefer launch_profiles naming\n\nRename the public launcher override concept to launch_profiles across the task list\nand docs, while keeping launch_scripts as a compatibility alias for older device

Browse Source 
records. Update the Svelte resolver to read both keys so per-device tweaks remain
backward compatible during the transition.
This commit is contained in:
Scott Idem
2026-05-13 10:26:01 -04:00
parent 8dd22912c3
commit b697126495
5 changed files with 29 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
documentation/PROJECT__AE_Events_Launcher_Native_integration.md
View File

@@ -199,15 +199,17 @@ temp directory (after the atomic copy from cache).
### Where to Configure
Templates are resolved in priority order by `get_launch_script_template()` in
Launch profiles are resolved in priority order by `get_launch_profile()` in
`launcher_file_cont.svelte`:
1. **`event_device.data_json.launch_scripts`** — API-driven, per-device. Highest priority.
1. **`event_device.data_json.launch_profiles`** — API-driven, per-device. Highest priority.
Set via the `event_device` record (Pres Mgmt → Device Management or direct DB edit).
2. **`$events_loc.launcher.launch_scripts`** — Local persistent config. Editable via the
2. **`$events_loc.launcher.launch_profiles`** — Local persistent config. Editable via the
Launcher config UI (planned) or direct `localStorage` manipulation.
If neither is set, `script_template` is `null` and Electron uses its built-in hardcoded defaults.
Legacy `launch_scripts` keys remain accepted as compatibility aliases in the resolver so older
device records continue to work while the preferred schema is `launch_profiles`.
### Key Format