Skip to content

Process custom apps in the Omarchy v4 branch - #118

Merged
bjarneo merged 1 commit into
omacom:mainfrom
Saco93:fix/process-custom-apps-in-v4
Aug 19, 2026
Merged

Process custom apps in the Omarchy v4 branch#118
bjarneo merged 1 commit into
omacom:mainfrom
Saco93:fix/process-custom-apps-in-v4

Conversation

@Saco93

@Saco93 Saco93 commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

What

ApplyTheme only ran template.ProcessCustomApps in the pre-v4 path. On Omarchy v4 installs (isOmarchyV4), the dedicated v4 template renderer skipped it entirely, so any templates a user placed in ~/.config/aether/custom/ were silently never generated.

Changes

internal/theme/writer.go: run template.ProcessCustomApps(themeDir, variables) in the v4 path too, with the same warning-on-failure handling as the legacy path.

Verification

  • make test passes (all internal + cli packages).
  • go vet clean.
  • Non-v4 behavior unchanged.

ApplyTheme only ran template.ProcessCustomApps in the pre-v4 path. On
Omarchy v4 installs (isOmarchyV4) the dedicated v4 template renderer
skipped it entirely, so templates in ~/.config/aether/custom/ were
never generated.

Run ProcessCustomApps in the v4 branch too, with the same warning-on-
failure handling as the legacy path. All tests pass.
@Saco93
Saco93 force-pushed the fix/process-custom-apps-in-v4 branch from 25ceb05 to a12ea33 Compare August 18, 2026 04:43
@bjarneo
bjarneo merged commit a44089f into omacom:main Aug 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants