You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
chore: stale kind-range docs and a deprecated manifest key #181
The kind: doc lines in src/context.mach (around lines 3407 to 3534) give the range as theme.LABEL .. theme.SCRIM, but built-in kinds now run past SCRIM (FOCUS_RING, and SLIDER_FILL from feat: slider value fill #167). They should name the range in a way that does not go stale when a kind is added.
Every manifest (mach.toml and each demo's) sets default = true under [target.linux-x86_64], which mach now warns is deprecated and has no effect.
Acceptance
The kind-range docs are correct and do not name the last kind
No manifest sets the deprecated key, and building the root and each demo prints no warning from the manifests
Activity
docs(#181): do not name the last theme kind in kind docs
chore(#181): drop deprecated default key from target tables
chore(#181): drop the panel demo's unused bool import
Merge pull request #188 from briar-systems/chore/181