@fusion.dev/helix 0.30.2 → 0.31.0

package/types/vue.d.ts

@@ -5558,8 +5558,10 @@ answer, and asking them to encode it as thresholds so this can decode it
 again is a worse API than letting them say it.
 
 Not reflected. Nothing selects on it: the band reaches the stylesheet as
-`data-band` on the fill, because that is the element being colored, so
-reflecting here would write an attribute onto the host for no reader. */
+`data-band` on the fill, because that is the element being colored, and a
+stylesheet outside as `indicator-good`, `-fair` or `-poor` among the fill's
+part names, so reflecting here would write an attribute onto the host for
+no reader. */
   band?: (HelixMeter["band"]) | undefined;
   /** Bottom of the high band.
 
@@ -11590,7 +11592,7 @@ export interface WcToolkitVueGlobalComponents {
     HelixPaginationVueProps,
     HelixPaginationVueEvents
   >;
-  /** A 'Select', laid out on one row. Every other field stacks its label because it stands in a column of fields; this one stands in a footer beside a run of page numbers, where a two-line control makes the whole row two lines tall.  'Select''s own parts are exported, so '::part(trigger)' and '::part(label)' reach through both boundaries and a consumer styles it as the select it is. */
+  /** A 'Select', laid out on one row. Every other field stacks its label because it stands in a column of fields; this one stands in a footer beside a run of page numbers, where a two-line control makes the whole row two lines tall.  'Select''s own parts are exported under 'control-', so '::part(control-trigger)' and '::part(control-label)' reach through both boundaries and a consumer styles it as the select it is. */
   "helix-pagination-size": DefineCustomElement<
     HelixPaginationSize,
     HelixPaginationSizeVueProps,