@flywheel-io/vision 21.8.1 → 21.8.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@flywheel-io/vision",
-  "version": "21.8.1",
+  "version": "21.8.2",
   "description": "Flywheel UI elements provided as Angular components and native web components",
   "author": "Flywheel",
   "license": "MIT",

package/types/flywheel-io-vision.d.ts

@@ -1328,10 +1328,30 @@ declare class FwFormRendererComponent {
      * re-runs validation so the field that was just blurred shows its errorText immediately
      * (validateFields only assigns errorText for touched controls, and the blurred control's
      * CVA already marked it touched before this native `focusout` handler runs). Wired to the
-     * form's `focusout` so fields only appear/disappear/error once a field loses focus, rather
-     * than on every keystroke.
+     * form's `focusout` so continuous (typed) fields only appear/disappear/error once a field
+     * loses focus, rather than on every keystroke. Discrete fields (radio/select/checkbox/switch/
+     * date) don't need to wait for this — see recomputeIfDiscreteChanged.
      */
     onFieldBlur(): void;
+    /**
+     * Recomputes visibility immediately (independent of focus/blur) when a *discrete* field's
+     * value changed on this tick — e.g. a radio/select/checkbox/switch/date selection. Those
+     * controls commit their value in a single click rather than keystroke-by-keystroke, so there's
+     * no "flicker while typing" concern gating them behind onFieldBlur, unlike text-style inputs.
+     *
+     * This also sidesteps a DOM event-ordering race specific to controls whose native element
+     * fires its own `focusout` (e.g. a radio `<input>`): clicking a different option in the same
+     * group fires `focusout` on the previously-focused option — bubbling up and running
+     * onFieldBlur — before `change` fires on the newly-clicked option and writes its value into
+     * the FormGroup. onFieldBlur alone would therefore always evaluate against the *previous*
+     * selection. Recomputing here, from the value-change itself, evaluates against the value that
+     * actually just changed.
+     *
+     * Returns whether visibility was recomputed, so the caller can re-run validation against the
+     * updated requiredByKey.
+     */
+    private recomputeIfDiscreteChanged;
+    private applyVisibility;
     /**
      * Marks every control touched/dirty and triggers validation immediately, then flips
      * validation into live (onChange) mode for the remainder of the form's lifetime. Call