@pathscale/ui 2.7.0 → 2.7.2

package/dist/components/_shared/material.css

@@ -195,7 +195,7 @@
     .ui-select__trigger,
     .language-switcher__trigger,
     .dropdown__trigger,
-    .toggle__track,
+    .switch__control,
     [data-control-material="solid"]
   ):not([data-control-material="glass"]) {
     background-color: rgb(

package/dist/layouts.manifest.json

@@ -1,7 +1,7 @@
 {
   "format": "solid-layouts-library-v2",
   "package": "@pathscale/ui",
-  "version": "2.7.0",
+  "version": "2.7.2",
   "components": {
     "Accordion": {
       "kind": "embedded"

package/dist/styles/glass.d.ts

@@ -68,8 +68,18 @@ export declare const GLASS_LIMITS: {
         readonly max: 1;
     };
 };
-/** What the shipped themes use. Both land on the same numbers. */
-export declare const GLASS_DEFAULTS: Record<GlassMode, GlassTuning>;
+/**
+ * What the shipped themes use. Both land on the same numbers.
+ *
+ * Typed with every axis required, unlike `GlassTuning` itself. A theme may
+ * leave `controlTint` unset, but the defaults are what an unset axis resolves
+ * *to*, so there is nothing left to be undefined here. Typed as a plain
+ * `GlassTuning` it read back as `number | undefined` for callers that index it
+ * by a computed axis - `GLASS_DEFAULTS[mode][axis]`, which is exactly how a
+ * settings panel drives one slider per axis - and every one of those call sites
+ * broke on a value this object never contains.
+ */
+export declare const GLASS_DEFAULTS: Record<GlassMode, Required<GlassTuning>>;
 /**
  * The `--glass-*` custom properties three numbers imply.
  *

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pathscale/ui",
-  "version": "2.7.0",
+  "version": "2.7.2",
   "author": "pathscale",
   "repository": {
     "type": "git",