Skip to content
This repository was archived by the owner on Jul 24, 2026. It is now read-only.

feat: add a startup environment check - #20

Merged
trin94 merged 2 commits into
mainfrom
feat/startup-environment-check
Jul 18, 2026
Merged

feat: add a startup environment check#20
trin94 merged 2 commits into
mainfrom
feat/startup-environment-check

Conversation

@trin94

@trin94 trin94 commented Jul 18, 2026

Copy link
Copy Markdown
Owner

Adds a DMS startupCheck that compiles the entry points and blocks loading with an explanatory toast when the environment is incompatible. Closes #6

trin94 added 2 commits July 18, 2026 14:34
We have no control over the installed DMS and Quickshell versions.
When an incompatible version breaks an import, the widget silently
disappears and the only trace is a log line.

DMS gates plugin loading on an optional startupCheck component, so
use it: compiling the entry points catches missing modules and
types across all our imports, and DMS turns the failure into a
toast that tells the user what is wrong instead of inviting a bug
report. Property level and behavioral drift still slip through,
this only upgrades the loudest failure class.

Closes #6
The manifest switched to the components map when the daemon split
landed, and DMS only understands that map since 1.5.0. Older
versions reject the manifest before any plugin code runs, so the
1.4 floor has been wrong since then. The new startup check needs
1.5.0 as well.
@trin94
trin94 merged commit 1b06f75 into main Jul 18, 2026
1 check passed
@trin94
trin94 deleted the feat/startup-environment-check branch July 18, 2026 12:49
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Harden against untested/uncontrollable environments

1 participant