pcm-shared-components 2.1.410 → 2.1.412

package/dist/components/Reservation/AnimalVehicleDetailsEditor/fieldTypeControl.js

@@ -18,15 +18,17 @@ export const openNativeDatePicker = e => {
   }
 };
 
-// Collapsed size for a notice's rich-text content before it needs a "Show More" link -- kept
-// deliberately small (3 text lines, clamped on a clean line boundary with an ellipsis via
-// -webkit-line-clamp) so a long admin-entered notice doesn't dominate the panel's vertical space;
-// anything longer is offered in full through the dialog below. Short content still renders in
-// full with no link at all (overflow-measured, not char-counted). NOTICE_COLLAPSED_MAX_HEIGHT is
-// only a fallback ceiling for engines without line-clamp support, sized generously enough that
-// the line-clamp is what actually cuts in normal browsers.
-const NOTICE_COLLAPSED_LINES = 3;
-const NOTICE_COLLAPSED_MAX_HEIGHT = 130;
+// Collapsed size for a notice's rich-text content before it needs a "Show More" link -- clamped
+// on a clean line boundary with an ellipsis via -webkit-line-clamp so a long admin-entered notice
+// doesn't dominate the panel's vertical space; anything longer is offered in full through the
+// dialog below. Short content still renders in full with no link at all (overflow-measured, not
+// char-counted). 6 lines, not fewer: Quill content routinely contains blank spacer paragraphs
+// (<p><br></p>) between sections, and each spacer costs a clamp line -- a tighter clamp left only
+// a couple of REAL text lines visible, which read as "not enough" in practice.
+// NOTICE_COLLAPSED_MAX_HEIGHT is only a fallback ceiling for engines without line-clamp support,
+// sized generously enough that the line-clamp is what actually cuts in normal browsers.
+const NOTICE_COLLAPSED_LINES = 6;
+const NOTICE_COLLAPSED_MAX_HEIGHT = 200;
 
 /**
  * The control for a `notice` field: the admin's sanitized rich text inside a bounded-height

package/dist/components/Reservation/AnimalVehicleDetailsEditor/index.js

@@ -92,6 +92,7 @@ export const AnimalVehicleDetailsEditor = props => {
     canAddMore,
     maxItems,
     showHistoricalAnswers,
+    extraLiveKeys,
     bare,
     className,
     theme,
@@ -455,7 +456,12 @@ export const AnimalVehicleDetailsEditor = props => {
       }, requiredErrorText(field.type)));
     }));
   })())), showHistoricalAnswers && selectedItem && (() => {
-    const liveKeys = new Set(fieldConfig.map(f => f.key));
+    // extraLiveKeys covers keys this component's own fieldConfig doesn't include but which
+    // are still genuinely live -- e.g. a once-per-reservation field, rendered by a sibling
+    // component (AnimalFieldsOnceBlock) but written into this same item's `values` object.
+    // Without this, a currently-checked notice/once field reads as a retired one the moment
+    // its value is set, since this component never saw it in its own fieldConfig.
+    const liveKeys = new Set([...fieldConfig.map(f => f.key), ...extraLiveKeys]);
     const historicalEntries = Object.keys(selectedItem.values || {}).filter(k => !liveKeys.has(k)).map(k => ({
       key: k,
       value: selectedItem.values[k]
@@ -615,6 +621,7 @@ AnimalVehicleDetailsEditor.defaultProps = {
   canAddMore: true,
   maxItems: 0,
   showHistoricalAnswers: true,
+  extraLiveKeys: [],
   bare: false,
   className: 'w-full',
   theme: undefined,
@@ -665,6 +672,13 @@ AnimalVehicleDetailsEditor.propTypes = {
    * since-retired answer on an EXISTING reservation is legitimate. A guest-facing booking widget
    * creating a brand-new reservation has no history to show and should pass false. */
   showHistoricalAnswers: PropTypes.bool,
+  /** Keys that should count as "live" for the Historical Answers check above even though they
+   * aren't in this instance's own `fieldConfig` -- for a caller that splits one lot's field list
+   * across two sibling components sharing the same item's `values` object (e.g. once-per-
+   * reservation fields rendered by AnimalFieldsOnceBlock instead of this component's own grid).
+   * Without this, a currently-answered field owned by that sibling component reads as retired the
+   * moment its value is set, since this component never sees it in its own fieldConfig. */
+  extraLiveKeys: PropTypes.arrayOf(PropTypes.string),
   /** Skip this component's own outer card (background/border/rounding) and render a plain
    * fragment instead -- for a caller placing this editor and AnimalFieldsOnceBlock's fields inside
    * one shared outer card. Defaults to false so every existing usage keeps its current look. */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pcm-shared-components",
-  "version": "2.1.410",
+  "version": "2.1.412",
   "private": false,
   "main": "dist/index.js",
   "babel": {