Skip to content

chore: stale kind-range docs and a deprecated manifest key #181

Closed

Description

@octalide

What

Two pieces of maintenance:

  • 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

  1. added
    patchBackwards-compatible bug fix or maintenance update
    choreMaintenance, refactor, or non-functional code change
    on Oct 1, 2026
  2. added 3 commits that reference this issue on Oct 1, 2026
  3. added a commit that references this issue on Oct 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    choreMaintenance, refactor, or non-functional code changepatchBackwards-compatible bug fix or maintenance update

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions